No, I am not using IIS as a front-end - my front-end is simply JSP pages. I have read that there are others with similar problems to this when using IIS as a front-end - no answers though just problem reports.
Eddie -----Original Message----- From: Tobias Meyer [mailto:[EMAIL PROTECTED] Sent: 07 November 2005 13:21 To: Tomcat Users List Subject: Re: Tomcat 5.0.28 session timeout / invalidation Are you using IIS as frontend on that machine? That is where I have very similar problems... I'll be very much interested in any findings regarding this topic. Tobias Edward Wynn wrote: >Hello, > > > >I am running Tomcat 5.0.28 and am having some problems with session >invalidation / timeout that I would like some help with. > > > >My application has a session-timeout of 5 minutes, and in my development >and test environments sessions are correctly invalidated by tomcat when >the timeout period is reached. At this point my class (method >valueUnbound) which implements HttpSessionBindingListener is called and >I am able to tidy up the session as I require. > > > >In my production environment I am coming across a problem where some >(but not all) sessions are not being invalidated once the timeout period >elapses. I have written some extensions to the manager application that >allow me to list all sessions for a Context and to subsequently force an >invalidation of sessions whose idle time is greater than a parameter I >pass to the tool. Using these tools I can see long lists of sessions >with idle times far in excess of 5 minutes - if I leave the system long >enough the idle times extend into 48 hours and beyond... If I then use >my tool to force session invalidation I can locate and invalidate these >sessions - at which point my valueUnbound method is run and session >clean up executes as expected - to me this proves that there is nothing >inherently wrong with the session itself (i.e once it is invalidated it >can be cleaned up as desired - there is nothing in the session that is >stopping this clean-up). > > > >I have spoken to the groups of users most affected by this problem and >have gone to great lengths to try to reproduce the problem in my test >environment using the same systems / connection methods and system usage >methods as they do but I have not managed to reproduce the problem. > > > >I have compared the configuration of the machines and they are identical >except that in production I have commented out the following default >connectors: SSL Coyote, AJP1.3 and Proxied HTTP 1.1 - in other words >only the non-SSL Coyote HTTP 1.1 connector is available. > > > >Has anyone else come across this or a similar problem? > >What did you do to fix it? > >Has anyone any advise or pointers on what they think might be wrong >here? > >Could someone offer a brief explanation of how Tomcat session expiry >works so that I would know which areas to focus my attention on? > > > >Many thanks in advance, Eddie > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
