Mon Mar 15 16:08:45 2004 warn (OS 121)The semaphore timeout period has expired. : winnt_accept: Asynchronous AcceptEx failed.
Mon Mar 15 16:08:45 2004 warn (OS 64)The specified network name is no longer available. : winnt_accept: Asynchronous AcceptEx failed.
Mon Mar 15 16:08:45 2004 warn (OS 64)The specified network name is no longer available. : winnt_accept: Asynchronous AcceptEx failed.
Mon Mar 15 16:08:45 2004 warn (OS 64)The specified network name is no longer available. : winnt_accept: Asynchronous AcceptEx failed.
Mon Mar 15 16:08:45 2004 warn (OS 64)The specified network name is no longer available. : winnt_accept: Asynchronous AcceptEx failed.
Mon Mar 15 16:08:45 2004 warn (OS 64)The specified network name is no longer available. : winnt_accept: Asynchronous AcceptEx failed.
Mon Mar 15 16:08:54 2004 warn (OS 64)The specified network name is no longer available. : winnt_accept: Asynchronous AcceptEx failed.
Mon Mar 15 16:08:54 2004 warn (OS 64)The specified network name is no longer available. : winnt_accept: Asynchronous AcceptEx failed.
Unfortunately, this didn't show up until we went live and put a load on the machine. Now, serving 400,000-500,000 scripts a day produces error files that are 200-500KB. Today was even worse, 2.5MB of errors. Rebooting sometimes helps for a while, but still, the server definately dies for anywhere from a few seconds to a few minutes.
So, I have two questios:
1) Has anyone gotten around the problems with mod_perl in Windows? If so, how?
2) I installed a trial version of PerlEx today which appears to work perfectly with my modified mod_perl scripts by only adding the PerlEx::DBI call. Is PerlEx ready for prime time or will have different problems with it?
Thanks,
Rod
In reply to Is mod_perl for Windoze not ready for prime time? by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |