Heh, I feel a bit silly now; turns out it was a serialization error, and the reason why it was happening at every page was because it was occurring in the MenuHelper ^^ Thanks all!
Regards, Ces On Thu, Dec 10, 2009 at 12:14 PM, [email protected] <[email protected]>wrote: > Hi, > > Check that session cookies are not mixed up between the application > servers. I had PageExpired exceptions when testing the same application on > the very same browser with WebLogic and Tomcat, and that was caused by that > both servers are using the JSESSIONID cookie, but with different paths, so > actually there was two JSESSIONID cookies appearing in the browser. And > because wrong cookie was picked up the session was always recreated, which > was causing PageExpired exceptions. The easy solution was to configure > WebLogic to use an other cookie name, and after that everything worked fine. > For testing just clear the cookies in your browser before/when switching > between app servers. > Cheers, > Zoltan > > Early Morning írta: > > Well yes, ideally, but it is easier to not use such a heavy appserver when >> developing, so we make do with an internal QA deployment on Glassfish :) >> In >> any case, I was more wondering about the differences between how >> appservers >> handle wicket page versions and the like, since I'd like to understand why >> such differences exist. In any case, I'll check for serialization errors >> first. Thanks! >> >> >> Regards, >> >> Ces >> >> On Thu, Dec 10, 2009 at 5:52 AM, <[email protected]> wrote: >> >> >> >>> Hi, >>> >>> It is usually easier to have identical development and production >>> platforms. If then you get an error as you describe, you usually catch >>> it in development before it reaches production. >>> >>> So why don't you develop with GlassFish? >>> >>> >>> Bernard >>> >>> >>> >>> On Thu, 10 Dec 2009 02:36:49 +0800, you wrote: >>> >>> >>> >>>> Hi all, >>>> >>>> Currently I have a problem with my application wherein when I press the >>>> >>>> >>> Back >>> >>> >>>> button of the browser and navigate to a new page, I get a Page Expired >>>> >>>> >>> error >>> >>> >>>> consistently. However, this only happens when my application is deployed >>>> >>>> >>> in >>> >>> >>>> Glassfish, but not when I run it using Jetty. Any suggestions for what I >>>> should check? >>>> >>>> Related to that, I also experienced an error wherein there was a >>>> target.add(form) in the onSubmit method of the button, which caused an >>>> Exception in Glassfish whenever the feedback panel within the form was >>>> >>>> >>> added >>> >>> >>>> because the page could not be constructed; however In Jetty, the same >>>> code >>>> caused no errors. The fix (removing target.add(form)) was simple enough, >>>> >>>> >>> but >>> >>> >>>> I was hoping someone could enlighten me regarding how different >>>> appservers >>>> handle wicket page versions, etc. Is there a resource I can look up for >>>> this? Thanks! >>>> >>>> >>>> Regards, >>>> >>>> Ces >>>> >>>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >>> >>> >> >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
