so it seems a terracotta problem or config problem... What kind of session store are you using?
On Thu, May 15, 2008 at 11:15 AM, richardwilko < [EMAIL PROTECTED]> wrote: > > Hi, > > I almost have clustering working now - thanks for all the help people have > given me. > > However keep seeing page exprired errors, specifically on a page that has > an > ajax lazy load panel on it. the page will load fine, but when the lazy > load > code executes the app throws a page expired error, a bit of digging arround > shows me that wicket cannot find the page it has just created in session. > I > am sure that its the ajax request from the lazy load panel as if I turn off > javascript the page loads fine. > > This does not happen when I dont use terracotta clustering. > > We are using jetty 6.1.9, terracotta 2.5.4, wicket 1.3.3. Whats strange > is > that even after I get the page expired error and go back into my app I > still > have the same jsessionid and looking at the session data in terracotta I > see > that I still have the same session. Also this doesn't occur on every page > with lazy loaded components, just one of them. > > Its like the session isnt updated before the ajax lazy load panel call is > made. > > Can anyone shed any light on this? I've spent way too much time getting > clustering to work already... > > Thanks, > > Richard > -- > View this message in context: > http://www.nabble.com/Page-expired-using-LazyLoadPanel-and-clustering-tp17249134p17249134.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] > >
