Cody Lerum created WFLY-3704:
--------------------------------
Summary: WebSocket Sessions must be manually closed
Key: WFLY-3704
URL:
https://issues.jboss.org/browse/WFLY-3704
Project: WildFly
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 8.1.0.Final
Reporter: Cody Lerum
Assignee: Jason Greene
Currently if a Web Socket session goes inactive due to the browser shutting down or the
user closing a tab the browser does not send a close event to the server. This behavior
seems the same with Chrome and IE.
The underlying TCP socket is however inactive and can be confirmed by calling a
Session#isOpen which returns false. This will cause a build up of sessions unless the user
does something like
{code}
for (Session session : sessions) {
if (!session.isOpen()) {
session.close();
}
}
{code}
This would need to be done periodically by the application. Shouldn't the server
automatically close these sessions when the underlying socket goes inactive?
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)