https://bz.apache.org/bugzilla/show_bug.cgi?id=65408
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution|--- |FIXED
--- Comment #20 from Mark Thomas <ma...@apache.org> ---
I've finally managed to track down the root cause of this.
If an application attempts to send a WebSocket message concurrently with the
WwebSocket connection closing, it is possible that the application will
continue to use the socket after it has been closed. Because some objects
associated with the socket are pooled, this could cause problems.
This has been fixed in 8.5.x for 8.5.76 onwards.
The fix required back-porting a lot of changes to the connectors. Users that
implement their own Endpoints might see a compatibility issue due to these
changes. We will look at options to fix these compatibility issues on a case by
case basis as they are identified.
--
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
