https://bz.apache.org/bugzilla/show_bug.cgi?id=58835
Bug ID: 58835
Summary: wrong shutdown for websockets
Product: Tomcat 9
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: WebSocket
Assignee: dev@tomcat.apache.org
Reporter: publicoce...@gmail.com
When the container shutdowns , it commands directly to close all the sockets.
It is a too much simply solution.
You might add a handler before to do it , i could make particolar things before
to close sockets , for example sending a final message with particular
informations.... (Business logic status)
Developers would have the possibility to handle the shutdown phase.
In tomcat 9 , it closes abrubtly all the sockets,
in tomcat 8 , it was better in this case , but when you are sending a message
before to close a socket , it throws a exception because it dont flush the
previous messages.
The solution for me is simply to flush messages enqueued before to close and
add a callback onShutdown ....
--
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
