No connection closed event when stopping Tomcat app about eventsource HOT 1 CLOSED

If I understand correctly, a full shutdown of tomcat will trigger the onerror event in the client.
However, only stopping the server app, but not tomcat, does not trigger the onerror event in the client.

From the EventSource's perspective, the client either has an open http connection or it does not. When the server interrupts the http connection, the onerror event is triggered.

It sounds like stopping the server app doesn't close the http connection, and therefore, onerror isn't triggered in the client.

EventSource connections are long-lived http connections. It's not uncommon for web servers to not shut down until all HTTP connections have finished. With EventSource connections, this never happens, so the shutdown never completes.

You probably need to explicitly close all open EventSource connections before you shut down. Or figure out a way to make that happen automatically.

In Node.js there is https://github.com/isaacs/server-destroy to solve this problem - I'm not sure what's available for Tomcat.

from eventsource.