[
https://issues.apache.org/jira/browse/WICKET-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038926#comment-13038926
]
Mauricio Lopez-Soto edited comment on WICKET-3667 at 5/25/11 2:23 AM:
----------------------------------------------------------------------
Hi Martin,
We still have the problem and I managed to write a small application that can
be used to reproduced the problem. First let me tell you what the real
application does (not the small attached app):
We have a main page that is 'always' visible. This main page shows 'real time'
data by refreshing a Wicket Datatable every 5 seconds using AJAX. If the user
clicks on any of the links (usually CRUD operations), the application opens a
new browser window with another table (sometimes it can be a couple of tabs,
each tab holding a datatable) that allows the user to do the basic CRUD tasks.
Every time the user clicks on one the links, we noticed that we get a new
version of the page, for example:
-First click -> http://localhost/app/page1?5
-Second click -> http://localhost/app/page1?12
-Third click -> http://localhost/app/page1?19
and so on..
After a few versions (we believe 50 versions) of page1 have been created, the
main page expires (PageExpiredException). We have managed to delay this (we
still get some PageExpiredException-s, but we don't know if the cause is the
same) by changing the default values of the DefaultPageManagerProvider as you
suggested in an earlier comment. We set the getCacheSize() and
getMaxSizePerSession() to 0, but it does not seem rigth to us. Maybe we are
doing something wrong and clicking the same link should not be creating new
versions of the same page.
To reproduce this on the attached application (pageexpired.zip)
-Unzip
-run mvn eclipse:eclipse
-Run the application jetty:run
-open a browser: http://localhost:8080/pageexpired
-On the main page click the 'Pop Up Window' link several times, until the
pop-up page version reaches 51 or more. Do not refresh the main page or click
on the 'click me' link (maybe the ajax 'click me' link can be clicked, haven't
tried).
-When you see version 51 or higher on the pop up window
(http://localhost:8080/pageexpired/popup?53), click the 'click me' link on the
main page.
You will get a Page Expired Error. We are using 1.5- RC4.2. It also happens in
Tomcat.
Thanks
was (Author: mlopezsoto):
Hi Martin,
We still have the problem and I managed to write a small application that can
be used to reproduced the problem. First let me tell you what the real
application does (not the small attached app):
We have a main page that is 'always' visible. This main page shows 'real time'
data by refreshing a Wicket Datatable every 5 seconds using AJAX. If the user
clicks on any of the links (usually CRUD operations), the application opens a
new browser window with another table (sometimes it can be a couple of tabs,
each tab holding a datatable) that allows the user to do the basic CRUD tasks.
Every time the user the user clicks on one the links, we noticed that we get a
new version of the page, for example:
-First click -> http://localhost/app/page1?5
-Second click -> http://localhost/app/page1?12
-Third click -> http://localhost/app/page1?19
and so on..
After a few versions (we believe 50 versions) of page1 have been created, the
main page expires (PageExpiredException). We have managed to delay this (we
still get some PageExpiredException-s, but we don't know if the cause is the
same) by changing the default values of the DefaultPageManagerProvider as you
suggested in an earlier comment. We set the getCacheSize() and
getMaxSizePerSession() to 0, but it does not seem rigth to us. Maybe we are
doing something wrong and clicking the same link should not be creating new
versions of the same page.
To reproduce this on the attached application (pageexpired.zip)
-Unzip
-run mvn eclipse:eclipse
-Run the application jetty:run
-open a browser: http://localhost:8080/pageexpired
-On the main page click the 'Pop Up Window' link several times, until the page
version reaches 51 or more. Do not refresh the main page or click on the 'click
me' link (maybe the ajax 'click me' link can be clicked).
-When you see version 51 or higher on the pop up window
(http://localhost:8080/pageexpired/popup?53), click the 'click me' link.
You will get a Page Expired Error. We are using 1.5- RC4.2. It also happens in
Tomcat.
Thanks
> Once in a while we get random page expired on customers site
> -------------------------------------------------------------
>
> Key: WICKET-3667
> URL: https://issues.apache.org/jira/browse/WICKET-3667
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core
> Affects Versions: 1.5-RC3
> Environment: jetty,. tomcat, ff
> Reporter: Nino Martinez
> Assignee: Martin Grigorov
> Attachments: heartbeatProblem.zip, pageexpired.zip
>
>
> To reproduce the error just run the attached quickstart, and run it. Open 2
> browser instances with 8 tabs each pointing toward the server. Wait for page
> expired.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
