https://bz.apache.org/bugzilla/show_bug.cgi?id=63913
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution|--- |FIXED
--- Comment #12 from Mark Thomas <ma...@apache.org> ---
Thanks.
Neither the WebSocket code nor Tomcat's I/O code is expecting a
NullPointerException here which is why it bubbles all the way up to the
Processor which logs it and closes the connection.
I'm going to fix this by catching the NPE and wrapping it in an IOException
which is a better match for what is going wrong and is an Exception that the
code is designed to handle.
Fixed in:
- master for 9.0.28 onwards
- 8.5.x for 8.5.48 onwards
- 7.0.x for 7.0.98 onwards
--
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
