[
https://issues.apache.org/jira/browse/WICKET-4009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13094800#comment-13094800
]
bernard commented on WICKET-4009:
---------------------------------
Martin,
wait for one minute then press the button on the page, then after receiving the
expired page, press the browser back button.
Andera,
I get this on GlassFish. To get started with it quickly, you may want to
download NetBeans with Java EE support which includes GlassFish. Just open the
quickstart directly in NetBeans and run it from the context menu. It will
prompt you with a dialog on what server to run. At the first time, you must
register the installed GlassFish.
> 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)
> Reporter: bernard
> Attachments: 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
