You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2013/03/21 16:12:57 UTC

[Bug 54738] New: WebSocket messages does not set lastAccessTime to session, and after the session.maxIntervalTimeout() my session is deleted

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.toader@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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org

[Bug 54738] WebSocket messages does not set lastAccessTime to session, and after the session.maxIntervalTimeout() my session is deleted

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=54738

--- Comment #2 from Radu Toader <ra...@gmail.com> ---
At least there should be a way to setLastAccessed time to a session.

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org

[Bug 54738] WebSocket messages does not set lastAccessTime to session, and after the session.maxIntervalTimeout() my session is deleted

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=54738

Radu Toader <ra...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |radu.m.toader@gmail.com

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org

[Bug 54738] WebSocket messages does not set lastAccessTime to session, and after the session.maxIntervalTimeout() my session is deleted

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=54738

--- Comment #3 from Nick Williams <ni...@nicholaswilliams.net> ---
I have created an issue for this on the WebSocket API project JIRA [1]. You
will need to login/register on java.net to view and/or watch it for updates.
Registration is free.

[1] http://java.net/jira/browse/WEBSOCKET_SPEC-175

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org

[Bug 54738] WebSocket messages does not set lastAccessTime to session, and after the session.maxIntervalTimeout() my session is deleted

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=54738

Mark Thomas <ma...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID

--- Comment #1 from Mark Thomas <ma...@apache.org> ---
This should be raised with the WebSocket EG. It is not an implementation issue
(it might become one if the spec is changed).

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org