https://bz.apache.org/bugzilla/show_bug.cgi?id=57749
--- Comment #2 from Mark Thomas <ma...@apache.org> --- That was going to be my first question - how easy is this to reproduce. I took a quick look at the code. The only way the socket could be null is if the output buffer had been recycled. That would be triggered by a socket close or the end of the request/response. Seeing that the issue happened after the write completed, I wonder if this is the result of the socket being closed on the input side. It would help to know what the exception was. I think some additional logging is called to start with. -- 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
