https://issues.apache.org/bugzilla/show_bug.cgi?id=54738
Bug ID: 54738
Summary: WebSocket messages does not set lastAccessTime to
session, and after the session.maxIntervalTimeout() my
session is deleted
Product: Tomcat 7
Version: 7.0.37
Hardware: All
OS: All
Status: NEW
Severity: major
Priority: P2
Component: Servlet & JSP API
Assignee: dev@tomcat.apache.org
Reporter: radu.m.toa...@gmail.com
Classification: Unclassified
WebSocket messages does not set lastAccessTime to session, and after the
session.maxIntervalTimeout() my session is deleted
I have attributes on httpsession, and I check them every time I want to send a
message to browser-client through WebSocket.
If the client is not making any other requests to page like AJAX or open
another link, his sessions is deleted along with the attributes on the session.
I have implemented ping-pong from client to server on WebSocket, I could
reset the lastAccessTime of the session there, but the problem is that there is
no visibility to session's lastAccessedTime so there is no way you can change
it. The framework should do that for you.
I belive that a reset must be added whenever a message is received/send to/from
client through WebSocket.
--
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
