DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21425>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21425 AcceptEx failed [semaphore timeout period has expired] [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Asynchronous AcceptEx failed|AcceptEx failed [semaphore | |timeout period has expired] ------- Additional Comments From [EMAIL PROTECTED] 2004-01-16 05:27 ------- I've changed the title of this report to reflect the semaphore bug, since the "specified network name is no longer available" bug is a duplicate bug. Folks, don't file duplicate bug reports, it gives us extra [EMAIL PROTECTED] to slog through and ignore actually fixing any bugs. Now the semaphore bug is most interesting, I'm gonna suggest that it's internal to Windows, but it sure seems that the timeout on AcceptEx wasn't considering numerical overflow comparing 64 bit time datum. That's why you would only see the bug when start and end times begin on different offsets, and appear as negative values. I'll double check the code right now that *we* don't attempt to subtract time delta's with insufficient precision. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
