While the debugger is stopped at the breakpoint you can see what leads to this call in the stacktrace. If it is coming from the application code then you should fix it. If it is triggered by Wicket itself then please upgrade to 7.12.0 and try again. If it still does the same then please create a mini application that reproduces the problem and attach it to a ticket at https://issues.apache.org/jira/projects/WICKET/issues
On Wed, Feb 20, 2019 at 1:53 PM AliKhan <tanek...@gmail.com> wrote: > Thanks for your quick reply! > I have verified as you suggested to breakpoint at Session#bind(). This > method is called 2 times after the session is invalidated. Strange thing is > that when user login, bind() is called only 1 time but on session > invalidate > it is being called 2 times. > I did not bumped the wicket version yet though. I verified this with > version > 7.0.0. > > -- > Sent from: > http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
