So you can not reproduce it in your test environment? Look in your http logs and see if the urls that are returning 50X codes mostly have a search bot user agent. If you have a public facing site that is scraped by Google, et al, you will see these errors because they do not maintain a session, but record session-relative links.
-- Jeremy Thomerson http://www.wickettraining.com On Thu, Mar 19, 2009 at 5:16 PM, novotny <[email protected]> wrote: > > Hi Jeremy, > > I'm not seeing any serialization errors in my logs... I couldn't find > anything useful when I searched the archives, although I did see some stuff > regarding this error that could be ajax related. I guess the first step > would be to figure out which URLs could be triggering this behavior. Do you > have any ideas how I could get that info? > > Thanks, Jason > > > novotny wrote: > > > > > > Hi, > > > > Our log file in production is showing a lot of these type errors: > > > > > > org.apache.wicket.protocol.http.PageExpiredException: Cannot find the > > rendered page in session [pagemap=null,componentPath=1,versionNumber=0] > > at > > > org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequestCycleProcessor.java:190) > > at org.apache.wicket.RequestCycle.step(RequestCycle.java:1246) > > at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1366) > > at org.apache.wicket.RequestCycle.request(RequestCycle.java:498) > > at > > org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:444) > > > > Does anyone know what can cause this to happen? Also is there a way > (maybe > > a class or method I can override) to log the URLs that a user is hitting > > to maybe narrow this down? > > > > Thanks, Jason > > > > -- > View this message in context: > http://www.nabble.com/PageExpiredException-problems-tp22608403p22608868.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] > >
