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 2004/03/14 21:23:24 UTC

DO NOT REPLY [Bug 12069] - Creation of more HttpSession objects for one previously timed out session

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=12069>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=12069

Creation of more HttpSession objects for one previously timed out session

markt@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|Major                       |Enhancement
            Version|4.0.4 Final                 |4.1.30



------- Additional Comments From markt@apache.org  2004-03-14 20:23 -------
The HTTP state management spec (RFC 2109) does not discuss concurrent requests.

Implementing a solution to the problem you describe would be tricky. Tomcat 
would have to maintain a list of old and new sessions and check this in a 
thread-safe way when creating a new session because the old one expired. This 
isn't going to have positive impact on performance.

Previous requests along similar lines have not been implemented.

I am going to change this to an enhancement request for now but without a 
proposed patch from you or interest from a tomcat committer this is unlikely 
to be implemented.

You might have better luck with changing the architecture of the web app that 
creates the concurrent requests.

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