Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (athena.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: session-timeout not taking effect
Date: Tue, 14 Sep 2010 14:39:01 -0700
Message-ID: 
 <3A7B10AA0D19B94FA69B1E55ADD1788B083FC624@webmail.cardiacscience.local>
In-Reply-To: <AANLkTi=3pfCVgQJFm5NG-GkM9P9jazNC-MWHNsdYg8oH@mail.gmail.com>
Thread-Topic: session-timeout not taking effect
Thread-Index: ActUVT667Uejdo+QT7Wj+QHfS7t8yA==
References: 
 <3A7B10AA0D19B94FA69B1E55ADD1788B083FC484@webmail.cardiacscience.local>
 <AANLkTi=3pfCVgQJFm5NG-GkM9P9jazNC-MWHNsdYg8oH@mail.gmail.com>
From: "Debbie Shapiro" <DShapiro@cardiacscience.com>
To: "Tomcat Users List" <users@tomcat.apache.org>

I should add that I am neither a Java nor a Tomcat expert by any means.
Where would I find some of these settings?

I'm using IE to access this application.

Where would one enable the access log? I essentially have the entire
Tomcat installation using the defaults at installation, with the
exception that I have included the InetSoft application directory in the
webapps folder.

If I navigate to another website and immediately navigate back to the
InetSoft page, it first displays a page that the login has expired and
then prompts me to login again. It's only if I leave the page up that it
seems to not expire. My version of IE doesn't have tabs (I'm still on
6.0), so it's either change the current window to a new page or open a
new window.

I'm not sure how to determine that the session-timeout is anything other
than 30 minutes aside from looking at the web.xml file. Not familiar
with JConsole. I don't currently have the Tomcat manager running. I just
found the documentation concerning that part of the app and I will see
about getting that started. As I said, I have everything set to the
defaults...

=20
=20
=20
=20
=20
Debbie Shapiro, Data Warehouse Manager
Office: 425.402.2233=20

-----Original Message-----
From: Wesley Acheson [mailto:wesley.acheson@gmail.com]=20
Sent: Tuesday, September 14, 2010 10:41 AM
To: Tomcat Users List
Subject: Re: session-timeout not taking effect


On Tue, Sep 14, 2010 at 7:17 PM, Debbie Shapiro
<DShapiro@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.acheson@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
> <DShapiro@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-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org