Colin,
Setting session-timeout in web.xml calls setMaxInactiveInterval on the
session manager (note that the timeout in web.xml is in minutes and
the inactive interval is in seconds).
The session-timeout is set in webdefault.xml which is applied to every
web application, so if you've set maxInactiveInterval in a context.xml
file then it will be overridden by the webdefault.xml setting. Try setting
it instead in a jetty-web.xml file, which is applied to the web app AFTER
web.xml has been parsed.
cheers
Jan
Colin Canfield wrote:
> I am not 100%, but I think this is the equivalent of
> setMaxInactiveInterval in session manager. I have tried setting this but
> to no help, it still takes around 10 minutes to time out.
>
> Anyone out there had more success with time outs, or know of a different
> way to set it ?
>
> Regards, Colin
>
>
>> There is a session-timeout element in webdefault.xml that you might need
>> to have a look at.
>>
>>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>
http://xircles.codehaus.org/manage_email>
>
>
--
Jan Bartel, Webtide LLC |
janb@... |
http://www.webtide.com---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
