https://bz.apache.org/bugzilla/show_bug.cgi?id=57489
--- Comment #24 from Barry Coughlan <b.coughl...@gmail.com> --- (In reply to Remy Maucherat from comment #23) > This looks like what it should do however: call onError. Rethrowing in that > method is not allowed. Sorry for not being clear - I wasn't suggesting that throwing the exception was a good fix (I'm not very familiar with the code), I was just using it to demonstrate that the issue lies there. Other read errors that occur in WsFrameServer.onDataAvailable() throw up the IOException so that onError/onClose is called, but swallowing the IOException in isReady() means that the onClose is never called. -- 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
