[WICKET-4009] Page Lock on Browser Back Button after Page Expiry

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.5-RC7
• Fix Version/s: 1.5.1
• Component/s: wicket
• 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
• Assignee: Martin Tzvetanov Grigorov
• Reporter: bernard
• Created: 31/Aug/11 05:16
• Updated: 06/Sep/11 09:18
• Resolved: 06/Sep/11 07:26

Description

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.

Sub-Tasks

• Improve RequestLogger to not do anything after IPageManager#commitRequest(): Resolved