https://issues.apache.org/bugzilla/show_bug.cgi?id=51835
--- Comment #1 from Konstantin Kolinko <knst.koli...@gmail.com> 2011-09-16 16:27:14 UTC --- 1. Are you sure that it is not a bug in your logging? You are not telling much about it. E.g. maybe you are not taking into account that session id changes during authentication (since 6.0.21). 2. Note also, that expired sessions are not evicted immediately upon expiring, but only when background processing thread finds them. See "backgroundProcessorDelay" property in Configuration Reference. The default delay is 10 seconds. Though I think that the thread might be stuck somewhere, as it performs other tasks as well (e.g. autodeployment). 3. You have to find a proof that there indeed are sessions that have "last accessed time" more than (your configuration + interval between background processing runs) ago. The manager webapp can be used to view the list of active sessions. It would be much better if you'd find how to reproduce this. Note, that "Bugzilla is not a support forum". The questions on how to diagnose something must be directed to the users@ list. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
