https://issues.apache.org/bugzilla/show_bug.cgi?id=55171
--- Comment #6 from Mark Thomas <ma...@apache.org> --- (In reply to Niki Dokovski from comment #5) > Should we try to have the "future" get version with the timeout? Sending > close as a result of an exception is an error situation anyway. That is certainly worth looking at. Looking at the code, I wonder if there is a wider problem with blocking writes. As I can't reproduce this issue at the moment, it would be very helpful if the original reporter (Stoyan Boshev) could do find out (e.g. with a debugger) the value of SocketProcessor.status for those threads that are blocked at line 1542 of NioEndpoint. I suspect that they will show Tomcat is trying to close the connection but can't because of the lock. If that is the case I need to do some more thinking on how the blocking writes are handled. -- 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
