right, non-clustered and httpsessionstore = exceptions non-clustered and default session store = no exceptions (as far as i can see)
clustered and httpsessionstore = exceptions clustered and default session store = exceptions although our live site is running on a httpsessionstore (non clustered) and does not have these same problems. The only thing that's changes is that i upgraded from wicket 1.3.0 to 1.3.3 (for clustering support) and some slight changes to the page which breaks - but nothing that should be causing these errors, the lazy load panel is the same. ive also tried wicket 1.3.2 and get same errors. But I still cant work out why on one page all my ajax works fine regardless of session store or clustering and on a different page the ajax causes page expired exceptions. Johan Compagner wrote: > > if you dont use terra then you should use the DiskPageStore > with that store getting page expires shouldnt happen as long as the http > session is there. > > johan > > On Thu, May 15, 2008 at 3:55 PM, richardwilko < > [EMAIL PROTECTED]> wrote: > >> >> Ok, I've been playing around a bit more, and it turns out that this is >> not >> limited to when I do clustering with terrracotta, but happens when i run >> jetty normally. >> >> The page expired exception fires with this message >> >> Cannot find the rendered page in session >> [pagemap=null,componentPath=60:yellAdTop,versionNumber=0] >> >> as i understand it pagemapname=null is just the default page map, so that >> shouldnt be a problem. Im still at a loss as to why this happens though. >> >> >> >> >> Johan Compagner wrote: >> > >> > look at setAttribute then for the store >> > It should be but into the session in the detach of the request. >> > >> > On Thu, May 15, 2008 at 12:30 PM, richardwilko < >> > [EMAIL PROTECTED]> wrote: >> > >> >> >> >> I still get the same behaviour with the httpsessionstore. >> >> >> >> the problem seems to be that the page isnt put in the page map, so >> when >> >> the >> >> ajax call is made to lazy load the panel it cant access the page its >> on. >> >> >> >> looking at the http session data in the terracotta admin console i see >> >> that >> >> the AccessStackPageMap has a page map name set to null, and i cant >> find >> >> the >> >> page i should be on in the httpsession. >> >> >> >> >> >> >> >> if you use terracotta you shouldnt use the default DiskPageStore i >> >> believe >> >> but revert back to the 1.2 httpsessionstore.. >> >> >> >> >> >> -- >> >> View this message in context: >> >> >> http://www.nabble.com/Page-expired-using-LazyLoadPanel-and-clustering-tp17249134p17250260.html >> >> Sent from the Wicket - User mailing list archive at Nabble.com. >> >> >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> >> >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/Page-expired-using-LazyLoadPanel-and-clustering-tp17249134p17253801.html >> Sent from the Wicket - User mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > -- View this message in context: http://www.nabble.com/Page-expired-using-LazyLoadPanel-and-clustering-tp17249134p17255175.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
