Hi Dale, Wicket keeps the most recent page from each session in a deserialized state, in addition to writing it to disk. This is an optimization since most requests interact with only the most recent page. After restart, these deserialized pages will not be available, forcing Wicket to restore the page from disk. It's not really an error, and as you've observed should not affect the user.
I don't have the code with me to verify this explanation, but I'm pretty sure this is correct. Dan On Tue, May 1, 2012 at 5:19 PM, Dale Ogilvie <dale_ogil...@trimble.com>wrote: > What does this warning from our wicket 1.4.20 app signify? > > WARN org.apache.wicket.protocol.http.SecondLevelCacheSessionStore > PageMap deserialization - got nulll lastPage > > It seems to occur in a couple of situations: > > a) when the application is reloaded due to a web.xml change > b) when restarting the tomcat instance > > nothing out of the ordinary is being done here, just re-loading the app. > > Thanks > > Dale > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
