On Tue, Sep 14, 2010 at 7:17 PM, Debbie Shapiro <dshap...@cardiacscience.com> wrote: > Hi Wesley - > I logged in to my web app, ran a report and then left it alone for 45 > minutes. Came back and tried to run another report. I was expecting to > receive a prompt to login again, but instead it runs the second report. > I also have a case open with InetSoft on this, but they are pointing me > to my Tomcat configuration. > > > > > > > Debbie Shapiro, Data Warehouse Manager > Office: 425.402.2233 > > -----Original Message----- > From: Wesley Acheson [mailto:wesley.ache...@gmail.com] > Sent: Tuesday, September 14, 2010 9:48 AM > To: Tomcat Users List > Subject: Re: session-timeout not taking effect > > > On Tue, Sep 14, 2010 at 6:29 PM, Debbie Shapiro > <dshap...@cardiacscience.com> wrote: >> I am using Tomcat 7.0 on a Windows 2003 Server 64-bit OS. I'm using > the >> default settings for the web.xml file for session-timeout (30 > minutes), >> but for some reason, the sessions aren't timing out at this point for >> users of the web app. Is there some reason why this setting would be >> ignored? I'm using Tomcat 7.0 with an InetSoft business intelligence >> implementation. >> >> > > Session timeout is the time out for the session if no requests are > received from the client. What are the symptoms? > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
Hi Debbie, I wasn't saying that that was the problem exactly. There are a number of things you can do to check, just to rule it out. 1 . If you use firefox try the firebug plugin. Go to the net tab and run your test. Ensure no more requests are sent. 2. Enable the access log in tomcat. Ensure your requests aren't coming in more frequently than 1/2 an hour. 3. Run the test again but when you get the report. Navigate to another website. Leave it the half hour navigate back to the tomcat instance, check if your still logged in (Don't close the browser window for this test to be valid) 4. Ensure you aren't seeing cached versions of the pages. 5. Check if the session timeout is indeed set to half an hour. (Maybe this info is in jconsole I'm sure others on this list will know) If all this fails then it looks like you have a bug in tomcat on your hands. Test 1 2 and 3 aren't exclusive they all test the same thing. Take your pick. (personally I prefer 1 & 2) Regards, Wesley --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
