The problem is caused by AJAX polling, and it is not specific to Tapestry, but to how Java servlet containers manage sessions. I had similar one (AJAX polling with Jetty) and IIRC I solved it by implementing my own SessionHandler and SessionManager classes (subclassing and replacing ones provided by Jetty) that avoided "de-idling" sessions for AJAX-polling related paths.
Best regards, Cezary On Thu, Nov 10, 2016 at 9:26 AM, .. ... <vavricka.to...@gmail.com> wrote: > Hi, > > I am using tapestry 5.4.1 together with jetty 9.2.14.v20151106. > > I want to set inactive timeout. When users is doing nothing application > should logout after some time. > I set timeout by setting > webapp.getSessionHandler().getSessionManager().setMaxInactiveInterval(30) > to 30 seconds. Zone in webpage updates every 5 seconds. With these settings > session was unable to timeout. > > When I set maxInactiveInterval to one second, session expires as expected. > > Is there any way to have larger timeout than zone update interval? > > Vavricka >
