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=35746>. 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=35746 ------- Additional Comments From [EMAIL PROTECTED] 2006-09-30 16:12 ------- Let's not be narrow minded and let's not suggest tomcat is only good for http servicing on server farms. Tomcat can be deployed on embeded devices or appliance of all sorts that may not have the luxury, the capacity or the access right to poll a ntp server. Whenever a user (or the ntp update agent/service/deamon) sets the date/time, sessions may be lost. The only feed I can provide, which is sufficient for any willing tomcat developer, is some design sketches. 1-Thread.sleep(n) or Object.wait(n) will always delay by the given time even if system time changes (without interrupt() and notify[All]() interferences) 1-whenever a session is refreshed, instead of renewing (pushing in the future) its expiration time, the code should simply reset to 0 the session 'age'. 2-whenever the session manager check (60 seconds is the default I think), it should simply age the session (here age+=60000;) and assert its validity as expected. It's that simple. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
