https://bz.apache.org/bugzilla/show_bug.cgi?id=62799
--- Comment #2 from m...@blackmans.org --- Yes, it was set to 5000 milliseconds (i.e. 5 seconds). Well, we don't see this behaviour in Apache 2.2 with the prefork MPM and we do see it with Apache 2.4 in the event MPM. However, I can imagine that might not be important. There's a redhat article, https://access.redhat.com/solutions/1229213 which specifically recommends not setting the timeouts due to non-blocking sockets. We are using 1.2.42, so we haven't been hit by that 1.2.44 bug of course. I cannot reproduce the issue outside of a production environment at the moment. If EINPROGRESS is handled, why is it associated with a connection failure? I believe 115 should never be the cause of a connection failure. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
