Details
Major Description
Closing of SSE connection by client is not detected and handled on the server part.
This results in server leaking resources when it is the clients responsibility for deciding on the lifetime of SSE connection.
My particular scenario is:
Status notifications for devices manged by the server are sent to the client (browser), this is a continues stream. That stream lives until browser tab/window is closed, which results in client closing the underlying SSE connection.
SseSinkImpl is not informed of connection being closed.
At the same time the exception set in org.apache.cxf.jaxrs.sse.SseEventSinkImpl#dequeue
future.completeExceptionally(ex);
in case of channel being closed is not acted upon internally within SseSinkImpl.