We are seeing some strange behavior in our Prod environment where we occasionally see PageExpiredException, even though the user is actively using the site.
Below is the stack trace Cannot find the rendered page in session [pagemap=null,componentPath=0:lpContent:pageHeaderBoltOnListerPanel:placeHolderBoltOns:0:placeHolderBoltOn:editModalLink,versionNumber=0] Stack trace level: 10 class org.apache.wicket.protocol.http.PageExpiredException Cannot find the rendered page in session [pagemap=null,componentPath=0:lpContent:pageHeaderBoltOnListerPanel:placeHolderBoltOns:0:placeHolderBoltOn:editModalLink,versionNumber=0] org.apache.wicket.request.AbstractRequestCycleProcessor:resolveRenderedPage(451) org.apache.wicket.protocol.http.WebRequestCycleProcessor:resolve(139) org.apache.wicket.RequestCycle:step(1090) org.apache.wicket.RequestCycle:steps(1176) org.apache.wicket.RequestCycle:request(499) org.apache.wicket.protocol.http.WicketFilter:doGet(257) org.apache.wicket.protocol.http.WicketFilter:doFilter(127) The reason I am posting it here is that, when I was trying to debug into the issue, there is a call made to the PageStore to get the Page, which involves the FilePageStore. I was wondering if the Thread Synchronization problems on the FilePageStore are causing our Unexpected "SessionExpired" messages. When I discussed with the users they seem to indicate when that this happens when they are trying to click on links that open Modal windows Or close them, or other Ajaxy links, which essentially leaves the user on the same page. I think I read in the initial post that the Thread Synchronization problem could be an issue in single page applications. We are using Wicket 1.3.0 beta 2. Any thoughts? -- View this message in context: http://www.nabble.com/Thread-synchronization-problems-in-FilePageStore-tp11545253p17260717.html Sent from the Wicket - Dev mailing list archive at Nabble.com.
