https://bz.apache.org/bugzilla/show_bug.cgi?id=63931
--- Comment #7 from Mark Thomas <ma...@apache.org> --- >From the tone of comment #6 you appear to have forgotten that everyone here is a volunteer, providing you with help and assistance (at no cost) to use the software that you have been given (also at no cost). What makes this worse is that it has already been explained to you what is going wrong. An explanation that was provided within 2 hours of the issue being opened. Let me try again with more words. Something goes wrong. This is probably a timeout due to congestion at the client and/or network and/or Tomcat because one or more of those components can't handle the message volume. At the point something goes wrong Tomcat will: - throw an IOException that the application will see (based on the stack trace you provided) - close the session, triggering an onClose() event for the Endpoint that the application should handle If the application ignores the Exception and the onClose() event and continues to try and write messages you will see the IllegalStateException reported in the original report. That the application ignores / swallows / fails to handle the Exception is an application issue, not a Tomcat issue. This is something that needs to be fixed in the application, not in Tomcat. That the application ignores / swallows / fails to handle the onClose() event is an application issue, not a Tomcat issue. This is something that needs to be fixed in the application, not in Tomcat. You may wish to enquire with the Spring team what the application needs to do to ensure that it is notified when the onClose() event is triggered. The only area where Tomcat may be able to do more (and why this issue is still open rather than being resolved as INVALID) is preventing applications writing messages after a close frame has been written to the client. Even if we are able to improve that, the only difference you are likely to see is a difference exception if the application tries to write a message after the close frame has been sent. -- 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
