https://bz.apache.org/bugzilla/show_bug.cgi?id=65368
--- Comment #4 from Mark Thomas <ma...@apache.org> --- I can recreate this. It is caused when the client closes the connection cleanly when Tomcat expects the connection to remain open. Tomcat reads the TLS close message which gets handled in the "Something else went wrong block". The current message doesn't really reflect what is going on. I think returning -1 which will trigger an EOFException in the caller is a better, more consistent way to handle this. It also clearly signals what went wrong - Tomcat found a closed connection when it tried to do a read. -- 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
