Hi,
On Thu, Oct 3, 2013 at 10:09 AM, sidorczukp <sidorcz...@microinput.com>wrote: > Hi, > I set up session expiration in web.xml: > <session-config> > <session-timeout>1</session-timeout> > <tracking-mode>COOKIE</tracking-mode> > </session-config> > > and set up: > getApplicationSettings().setPageExpiredErrorPage( SignInPage.class ); > > but it doesn't work: > When tomcat session expired user is not redirecting to another site, but it > throws error with null session variable. > What is the stacktrace ? > > How can i handle it? I use: tomcat, spring, wicket. > > I found solution here: > http://my3java.blogspot.com/2013/04/handling-session-timeout-in-wicket.html This solution is not correct. It pings the application every minute so the session will never timeout. In case the page is actually used there is no code to tell the ajax behavior to reset itself. > > but I'm not sure if it is necessary and if it fix my issue. > > > > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Session-expired-controll-timeout-redirect-tp4661674.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
