DO NOT REPLY [Bug 37356] - Tomcat does not invalidate sessions after session-timeout period has passed.

[bu...@apache.org]

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=37356>.
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=37356





------- Additional Comments From pheraud@objetdirect.com  2007-02-22 07:40 -------
Created an attachment (id=19631)
 --> (http://issues.apache.org/bugzilla/attachment.cgi?id=19631&action=view)
A JSP That can be used to see the accessCount of a session

For people having doubts and still investigating about this bug, I put in
attachment a small JSP that you can put at the root of your web application to
see if the bug is happening.
You can log into your application and call this JSP (e.g.
http://localhost:8080/myWebApp/testSession.jsp) that will display the
accessCount of your session. Just do some refresh into your application ( on a
real page ) and refresh the testSession.jsp.
If you have no request pending, the displayed accessCount should be (1), if
it's greater, you triggered the bug.
On some of my applications, the accessCount takes 10 per each page, probably
trigggered by numerous GET request made by the browser for getting
CSS/Javascript files (even in pessimistic cache mode).

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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