[TYRUS-225] Invalidation of (Servlet) HttpSession does not invalidate
WebSocket Session Created: 31/Jul/13 Updated: 08/Aug/13 Resolved: 06/Aug/13
Status:
Project:
Component/s:
Affects
Version/s:
Fix Version/s:
Resolved
tyrus
None
1.0, 1.1, 1.2, 1.2.1
Type:
Reporter:
Resolution:
Labels:
Remaining
Estimate:
Time Spent:
Original
Estimate:
Environment:
Bug
martinandersson.com
Fixed
None
Not Specified
Issue Links:
Related
is related to TYRUS-230 When Session is invalidated, the clos... Resolved
1.3
Priority:
Assignee:
Votes:
Major
Pavel Bucek
0
Not Specified
Not Specified
All
Description
The Java API for WebSocket specification JSR-356 doesn't really talk about time outs. He says
on page 7 that there is a close code 1006 that has to be used "if the local container determines
the session has timed out". So apparently he takes a time out for granted and my improvement
suggestion is rather a bug report??
Anyways, I've force killed my browsers and waited for a long time for this time out to happen.
It doesn't. So I guess it isn't implemented at all. Could of course be really useful to have! Thing
is that half of all the browsers out there do not send a close code 1001 when we close the tab or
browser (required according to spec: http://tools.ietf.org/html/rfc6455). So I have to rely on
server timers to clean up after users that dropped. But like I said, apparently one doesn't even
have that. Hence my application will leak resources over time.
Comments
Comment by Pavel Bucek [ 06/Aug/13 ]
merged to the master branch (rev 599d21356d1504570d729d3f9e4136e87a7e6db5)
Generated at Wed Feb 10 04:03:10 UTC 2016 using JIRA 6.2.3#6260sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.