check your logs for serialization errors. Wicket isn't able to retrieve the page from the page cache if there are serialization errors. This often causes the page expiration message to appear.
Martijn On Fri, Jul 25, 2008 at 11:57 PM, dukehoops <[EMAIL PROTECTED]> wrote: > > Hi, > > My webapp's <session-timeout> is set to 30 minutes but some ajax requests > result in PageExpiredExceptions if AjaxSubmitLinks are clicked after about 5 > minutes of inactivity. > > Is there a timeout value for ajax requests (or page expiration timeout > values) that is distinct from HttpSession's timeout value? If so where is it > set and how can it be read/changed? > > thanks > -nikita > > ----- > ---------------- > Nikita Tovstoles > vside.com > ---------------- > > -- > View this message in context: > http://www.nabble.com/ajax-request-timeout-different-from-Session-timeout--tp18660284p18660284.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] > > -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.4 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
