Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
In-Reply-To: <55E0A3B7.6000301@christopherschultz.net>
References: 
 <OF15323FEC.C594BEAD-ON80257EAF.00581040-80257EAF.0058A42B@airmiles.co.uk>
 <55E0A3B7.6000301@christopherschultz.net>
To: "Tomcat Users List" <users@tomcat.apache.org>
MIME-Version: 1.0
Subject: Re: Tomcat 8 Session Timeout
Message-ID: 
 <OFE766A9AC.13F59DC2-ON80257EB3.002A619A-80257EB3.002B1BD7@airmiles.co.uk>
From: Theo.Sweeny@avios.com
Date: Tue, 1 Sep 2015 08:50:51 +0100
Content-Type: multipart/alternative;
 boundary="=_alternative 002B1BD680257EB3_="

--=_alternative 002B1BD680257EB3_=
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Chris,

That's pretty much it (except the path for the app's web.xml looks a
little odd).

We are running multi-instance environment and this is why the path is=20
$CATALINA_BASE/conf/web.xml

Are the web services specifying their own session-timeout in the
application-specific web.xml?

No the web-apps are not specifying their own session-timeout. We want to=20
run with a stateless environment. Eventually the session-timeout will be=20
brought down to 0, but the current setting for 2 minutes doesn't work. The=
=20
sessions do not timeout.

Theo


From:   Christopher Schultz <chris@christopherschultz.net>
To:     Tomcat Users List <users@tomcat.apache.org>,=20
Date:   28/08/2015 19:09
Subject:        Re: Tomcat 8 Session Timeout


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Theo,

On 8/28/15 12:08 PM, Theo.Sweeny@avios.com wrote:
> Hello - currently HTTP sessions are configured to timeout after 120
>  seconds, in $CATALINA_BASE/conf/web.xml
>=20
> <session-config> <session-timeout>2</session-timeout>=20
> </session-config>

I'd highly recommend that you move that configuration from
conf/web.xml to your own web application's web.xml.

> However this is not being honoured by the web services, where many
> session are lasting longer.
>=20
>> From what I understand - the order for session timeouts is -
>=20
> HttpSession.setMaxInactiveInterval(int)=20
> $WebApplication/webapp/WEB-INF/web.xml $TOMCAT_BASE/conf/web.xml
>=20
> Is there something that I'm missing?

That's pretty much it (except the path for the app's web.xml looks a
little odd).

Are the web services specifying their own session-timeout in the
application-specific web.xml?

- -chris
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQIcBAEBCAAGBQJV4KO3AAoJEBzwKT+lPKRYh8cQALjjzZ4glyywX4HrTpfAOtEJ
Ck1LC/S82MgNfCfS1dOx8fUpuER6ZSJ+fkALjAMjAr5MmQX+/Z2nODvj/XWDLkRj
6Hyp/F+rEnExt4bS6idWz32hPtzDqxA4Ffxy9oCROihXXdvA0qGn6xGfKwtUaBH2
rviw3au4uD2W3iPffszUj3VnGQnWhK3QFQpFCLkpVu1lF/EiqBCL3XHIY+6cDzBO
fpGWiFrk+9RSuP/uN3LEGzdZNvuHNiNu5OrlvBq9P8Q1zwya6fcuPGu0NvFD7ESl
o0pCmcie9NUFXN1R0/RtT8uw7ZVELWrPx5C6zLR1tbwodMnarlQMazAdQFDDtiVK
DLPjpKF0bPqAP3ORUzRAu3IfSaXhtgE77byAB8DLnPJjpKeyWEp4tCDP1CmI6NI1
5dVQmt5CJAo5pP5YAMM38GsJyY5NoQ2NI61tPJ/NFTJkV0pyCGlufiRMp6ySMvBP
zY8CjhNEjhfEV35RB1hYzawhZ3hgV3oq78HLGLZ15eaYiBTBHyHyKgdbitRfawIP
ICdvpuElYDPNKFI2SfSb3qQc64sm+kqN6B1DNWMALAWISNENB0ahu6D4a9UJTr0R
FgFRCdpkkV8/3FfpoSpu2kzzBubYMA7XpMyuk9HWlABJvT99AJCwPeA2C5falShv
j5HCHDLxsn1LzK8hl9mK
=3D3HRA
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org

---------------------------------------------------------------------------=
--------------------------------------------------------------
The Mileage Company Limited is a limited company registered in England unde=
r company number 2260073 whose registered office address is at
Astral Towers, Betts Way, London Road, Crawley, West Sussex, RH10 9XY.

This email and any files transmitted with it are confidential and intended =
solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify the s=
ystem manager.

This footnote also confirms that this email message has been swept by Mimec=
ast for the presence of computer viruses.=20
---------------------------------------------------------------------------=
--------------------------------------------------------------

--=_alternative 002B1BD680257EB3_=--