https://issues.apache.org/bugzilla/show_bug.cgi?id=54756
--- Comment #9 from Sebb <s...@apache.org> --- (In reply to comment #7) > I've taken a look at this and have found an issue in that errors on the > outbound side were silently swallowed when APR/native was being used. I > suspect the crash observed here is the result of continuing using a socket > that has already closed due to an error. > > I have fixed this particular issue and the fix will be in 7.0.40 onwards. What if the user code ignores the new error? Is it still possible for user code to continue using the socket? I had a look at the patch but it only seemed to report the error, but maybe I'm missing something and it's not possible to get at the closed socket using Java code external to Tomcat. It's good to report the error, but I would have thought the safest option would be to fix APR/native so it cannot be crashed externally - whether from Tomcat code or application code. -- 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
