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 [EMAIL PROTECTED] 2006-02-07 18:46 ------- (In reply to comment #11) > (In reply to comment #9) > > Please check this defect: 28846 > > > > I think it should be the same problem. :-) > > But that bug applies to the tapestry project. > Is the engine mentioned in that bug the tapestry engine or the tomcat engine? We're seeing this same issue, as well. We're using tomcat 5.5.4, and we appear to only see it in environments under heavy load when using the ajp13 connector. We have another customer redirecting from IIS and they're not experiencing this issue. I spent a couple hours looking at the code and I didn't see anything weird. What I can tell you is that for the sessions this occurs on, their inactivity time IS properly set, but they still don't get invalidated. When I call invalidate on those sessions, they ARE invalidated. We're not using the tapestry project at all--just Tomcat and Apache (or Tomcat and IIS). Those sessions which fail to invalidate stay around forever--or seemingly so. I've seen inactivity times in the 2500+ minutes range. -- 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]
