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 28131] - DeltaManager lost session expiration code line
Date Thu, 01 Apr 2004 18:30:24 GMT
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=28131>.
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=28131

DeltaManager lost session expiration code line





------- Additional Comments From rainer.jung@kippdata.de  2004-04-01 18:30 -------
Sorry, I just realized that isValid is supposed to expire the session. But in 
fact I can't see it expiring. I added some debug code to DeltaSession and I can 
see the following: Every time the session is checked for expiration the value 
of "accessCount" is 1. session.access increases it to 2 and session.Endaccess 
decreases is to 1. So it looks like the default value of access after creation 
of a new session object should be 0 instead of 1? If this is true, the same may 
apply to recycle.

---------------------------------------------------------------------
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