[
https://issues.apache.org/jira/browse/WICKET-4009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13097823#comment-13097823
]
Andrea Del Bene commented on WICKET-4009:
-----------------------------------------
Thank to you Martin. I made my question about expired session because I wanted
to understand how we ended up with a lock left assigned.
FOR INFORMATION: With a little more debugging I've found that when session is
expired but after commitRequest(), request logger asks for page class and
getPage(id) is called. So the logger should be the one who left a lock occupied
and caused the bug.
> Page Lock on Browser Back Button after Page Expiry
> --------------------------------------------------
>
> Key: WICKET-4009
> URL: https://issues.apache.org/jira/browse/WICKET-4009
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5-RC7
> Environment: Wicket version: 1.5-RC7
> java version "1.6.0_25"
> Java(TM) SE Runtime Environment (build 1.6.0_25-b06)
> Java HotSpot(TM) Client VM (build 20.0-b11, mixed mode, sharing)
> Server: GlassFish 3.1.1
> Reporter: bernard
> Assignee: Martin Grigorov
> Fix For: 1.5.1
>
> Attachments: pageManagerPatch.txt, pageManagerPatch.txt,
> quickStart.zip
>
>
> In the attached quickstart, after page expiry and browser back navigation, a
> server error occurs such as:
> "failed to acquire lock to page 0, attempted for 1 minutes out of allowed 1
> minute"
> This appears to be related to request logging, but I have seen other strange
> errors without request logging such as
> org.apache.wicket.request.handler.ComponentNotFoundException: Could not find
> component 'form' on page 'class web.page.ExpiredPage
> also with browser history back navigation.
> I have seen none of these errors in Wicket 1.4. I guess the reason for not
> having seen this before it that http cache headers are different in 1.5.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
