[WICKET-4733] AjaxSelfUpdatingTimerBehavior on unversioned page keeps triggering StalePageException when multiple tabs open

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.5.8, 6.0.0
• Component/s: wicket
• Assignee: Unassigned
• Reporter: Emond Papegaaij
• Created: 27/Aug/12 13:28
• Updated: 04/Jun/14 12:58

Description

When an AjaxSelfUpdatingTimerBehavior is used on an unversioned page, and the user opens the same page in a second tab, both pages will keep triggering StalePageExceptions. The following sequence of events occurs:
Tab 1 opens page (render count = 1)
Tab 2 opens page (render count = 2)
Tab 1 triggers Ajax update for rc=1, which triggers a StalePageException
Tab 1 gets redirected to a fresh page (render count = 3)
Tab 2 triggers Ajax update for rc=2, which triggers a StalePageException
Tab 2 gets redirected to a fresh page (render count = 4)
Tab 1 triggers Ajax update, etc, etc.

The attached quickstart demonstrates this problem. Open the home page, open the same url (with ?0) in a second tab. This will kill the refresher on the first tab. Now reload the first tab and both pages will keep refresh in an endless loop.

Issue Links

• relates to: WICKET-5607 Wicket Ajax fires calls scheduled by AbstractAjaxTimerBehavior even after unload of the page