tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 15463] - StandardManager incorrectly uses getLastAccessedTime
Date Mon, 03 Feb 2003 18:40:39 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15463>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15463

StandardManager incorrectly uses getLastAccessedTime





------- Additional Comments From pkhalife@dinmar.com  2003-02-03 18:40 -------
I've made the same observation.

I was implementing a session keep alive for a client, when I noticed the 
session's getLastAccessedTime() is not updating.

After some testing, I noticed the correct value is displayed for every second 
hit.

My current workaround is to hit the server twice for every keep alive i need.

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


Mime
View raw message