You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Sushila Burgess (Jira)" <ji...@apache.org> on 2022/05/16 13:47:00 UTC

[jira] [Updated] (WICKET-6983) ComponentNotFoundException after StalePageException

     [ https://issues.apache.org/jira/browse/WICKET-6983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sushila Burgess updated WICKET-6983:
------------------------------------
    Description: 
In very limited circumstances, immediately after a StalePageException, an unexpected runtime ComponentNotFoundException occurs. This problem was discovered by a professional tester, who has been testing the latest version of my Wicket 9.9.1 application. I have already described it on [StackOverflow|https://stackoverflow.com/questions/72203513/wicket-9-9-1-unexpected-runtimeexception-last-cause-component-xx-has-been-r] and Martin G advised me to report it here. As requested, I have developed a quick-start application which reproduces the problem in - as I have already mentioned - very specific, limited circumstances.

When running the application, the first page to appear is a dummy login page, with basic instructions for logging in. In summary, a drop-down list offers two usernames, "hasLinks" and "noLinks". Please select "hasLinks" and click the login button.

The next page will display a couple of links, plus the following instructions:
h2. How to reproduce the exception
 # Immediately after logging in as "hasLinks" in a *newly-opened* browser, duplicate your tab.
*N.B. the "jsessionid" must still be visible in the address bar.*
 # In the duplicated tab, click the "Log out" button at the bottom of the page.
 # Log back in again, this time as "noLinks".
 # Return to your original tab, where 2 links are still displayed.
 # Click on one of the links.
 # The exception occurs.

 

I am attaching a zip file containing the source of my quick-start application, with a war file in the target directory. I am also attaching the stack trace of the exception.

  was:
In very limited circumstances, immediately after a StalePageException, an unexpected runtime ComponentNotFoundException occurs. This problem was discovered by a professional tester, who has been testing the latest version of my Wicket 9.9.1 application, prior to release. I have already described it on [StackOverflow|https://stackoverflow.com/questions/72203513/wicket-9-9-1-unexpected-runtimeexception-last-cause-component-xx-has-been-r] and Martin G advised me to report it here. As requested, I have developed a quick-start application which reproduces the problem in - as I have already mentioned - very specific, limited circumstances.

When running the application, the first page to appear is a dummy login page, with basic instructions for logging in. In summary, a drop-down list offers two usernames, "hasLinks" and "noLinks". Please select "hasLinks" and click the login button.

The next page will display a couple of links, plus the following instructions:
h2. How to reproduce the exception
 # Immediately after logging in as "hasLinks" in a *newly-opened* browser, duplicate your tab.
*N.B. the "jsessionid" must still be visible in the address bar.*
 # In the duplicated tab, click the "Log out" button at the bottom of the page.
 # Log back in again, this time as "noLinks".
 # Return to your original tab, where 2 links are still displayed.
 # Click on one of the links.
 # The exception occurs.

 

I am attaching a zip file containing the source of my quick-start application, with a war file in the target directory. I am also attaching the stack trace of the exception.


> ComponentNotFoundException after StalePageException
> ---------------------------------------------------
>
>                 Key: WICKET-6983
>                 URL: https://issues.apache.org/jira/browse/WICKET-6983
>             Project: Wicket
>          Issue Type: Bug
>    Affects Versions: 9.9.1
>         Environment: Occurs on both Linux and Windows 10 Enterprise.
>            Reporter: Sushila Burgess
>            Priority: Major
>         Attachments: missinglink.zip, stacktrace.txt
>
>
> In very limited circumstances, immediately after a StalePageException, an unexpected runtime ComponentNotFoundException occurs. This problem was discovered by a professional tester, who has been testing the latest version of my Wicket 9.9.1 application. I have already described it on [StackOverflow|https://stackoverflow.com/questions/72203513/wicket-9-9-1-unexpected-runtimeexception-last-cause-component-xx-has-been-r] and Martin G advised me to report it here. As requested, I have developed a quick-start application which reproduces the problem in - as I have already mentioned - very specific, limited circumstances.
> When running the application, the first page to appear is a dummy login page, with basic instructions for logging in. In summary, a drop-down list offers two usernames, "hasLinks" and "noLinks". Please select "hasLinks" and click the login button.
> The next page will display a couple of links, plus the following instructions:
> h2. How to reproduce the exception
>  # Immediately after logging in as "hasLinks" in a *newly-opened* browser, duplicate your tab.
> *N.B. the "jsessionid" must still be visible in the address bar.*
>  # In the duplicated tab, click the "Log out" button at the bottom of the page.
>  # Log back in again, this time as "noLinks".
>  # Return to your original tab, where 2 links are still displayed.
>  # Click on one of the links.
>  # The exception occurs.
>  
> I am attaching a zip file containing the source of my quick-start application, with a war file in the target directory. I am also attaching the stack trace of the exception.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)