https://issues.apache.org/bugzilla/show_bug.cgi?id=57489
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
OS| |All
--- Comment #1 from Mark Thomas <ma...@apache.org> ---
Hmm. Whatever is going wrong, is going wrong earlier than this stack trace.
Something causes the WebSocket connection to close. It appears that Atmosphere
isn't notified about this / doesn't notice it.
Something happens later that causes Atmosphere to realise there is a dead
WebSocket connection. Atmosphere triggers a 'dirty' close.
This 'dirty' close fails because the WebSocket connection has already been
closed. That triggers an error because, as far as I can tell, a normal
WebSocket close reason (1000) is used. If abnormal closure was used (1006),
Tomcat would swallow any error.
What we really need to figure out is why is this connection closed in the first
place. There isn't much in the way of debug logging for WebSocket session
closure in Tomcat - I'll fix that for the next release - but it is worth seeing
is Atmosphere's debug logging tells you anything useful.
--
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
