I've seen this behavior too. My customers complain about their sessions timing out too quickly. I raised the setting, but we're still seeing problems. I'll try to add a listener, too.
On Thu, Jul 9, 2009 at 11:31 AM, Igor Vaynberg<igor.vaynb...@gmail.com> wrote: > sounds like tomcat is expiring the sessions early. i would add a > sessionlistener and log when the sessions are being expired. > > -igor > > On Thu, Jul 9, 2009 at 7:38 AM, Zhubin Salehi<zhooz...@gmail.com> wrote: >> Hi, >> >> >> I’m using Wicket 1.4-RC6, Tomcat 6.0.20 and JDK 1.5.0_19. The >> “session-timeout” timeout value in tomcat/conf/web.xml is 30, but I noticed >> my pages timeout after about 10 minutes. If I don’t touch a page for 10 >> mints, next time I submit a form on that page I get a “Page Expired” error. >> >> >> >> Any ideas what might be wrong? >> >> >> >> Thanks, >> >> Zhubin >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
