https://bz.apache.org/bugzilla/show_bug.cgi?id=58151
--- Comment #17 from Mark Thomas <ma...@apache.org> --- The stack trace only shows where execution is at a single point in time. It doesn't show how execution reached that point or where execution will go afterwards. I suspect that something is putting a socket in an odd/bad state. The code then enters the following loop: - the socket is queued to be added to the poller - the socket is added to the poller - poll() finds an event for the socket - the event is processed - processing terminates early because of the odd/bad state What we need to figure out is what is this odd/bad state so we can detect it and ensure the socket is correctly processed (probably closed). It is possible that a timeout fired while you were looking at the code. I'd recommend increasing the socket timeout to 5-10 minutes while you are debugging this. -- 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
