On 21/06/2016 03:54, mw...@loftware.com wrote:
>
>
>> -Original Message-
>> From: Mark Thomas [mailto:ma...@apache.org]
>> Sent: Monday, June 20, 2016 11:32 AM
>> To: Tomcat Users List <users@tomcat.apache.org>
>> Subject: Re: session-timeout a
> -Original Message-
> From: Mark Thomas [mailto:ma...@apache.org]
> Sent: Monday, June 20, 2016 11:32 AM
> To: Tomcat Users List <users@tomcat.apache.org>
> Subject: Re: session-timeout and maxInactiveInterval
>
> On 20/06/2016 16:00, mw...@loftware.com wrote
On 20/06/2016 16:00, mw...@loftware.com wrote:
> We are running 7.0.69 and Java 1.8.0_91.
>
> We ran into an incident at a customer where the customer had set
> session-timeout to 0 – which according to the servlet 3.0 spec, the
> session should never time out. However, the customer was
We are running 7.0.69 and Java 1.8.0_91.
We ran into an incident at a customer where the customer had set
session-timeout to 0 - which according to the servlet 3.0 spec, the session
should never time out. However, the customer was basically seeing the session
timeout immediately. When we
Question. I have been looking around the Net for information about the
items in the subject and tomcat; it appears that they are actually the
same thing(I'm not sure I'm understanding the docs correctly). So then,
what is the difference between the session-timeout that's set in a
tomcat's
From: Lynn Hollerman [mailto:gmh2...@louisiana.edu]
Subject: session-timeout vs. maxInactiveInterval
I have been looking around the Net for information about
the items in the subject and tomcat; it appears that they
are actually the same thing
Pretty much. The Manager setting is used
