https://issues.apache.org/bugzilla/show_bug.cgi?id=53829
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #2 from Mark Thomas <ma...@apache.org> ---
Firefox doesn't close the connection, so since WebSocket uses an infinite
timeout by default, Tomcat just sits and waits for Firefox so send some data.
As soon as I close Firefox, the thread is released.
Possible work-arounds are:
- use a different browser (e.g. Chrome it didn't time out after a couple of
minutes in my simple test)
- specify a read timeout for the WebSocket app and then use ping/pongs to keep
the connection alive
You may also want to report a bug against Firefox since the onClose() event is
firing but the socket is remaining open.
--
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
