You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Nino Martinez (JIRA)" <ji...@apache.org> on 2011/05/04 16:04:03 UTC
[jira] [Created] (WICKET-3667) Once in a while we get random page
expired on customers site
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
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
[jira] [Issue Comment Edited] (WICKET-3667) Once in a while we get
random page expired on customers site
Posted by "Mauricio Lopez-Soto (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (WICKET-3667) Once in a while we get random page
expired on customers site
Posted by "Mauricio Lopez-Soto (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mauricio Lopez-Soto updated WICKET-3667:
----------------------------------------
Attachment: 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.
> 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
[jira] [Commented] (WICKET-3667) Once in a while we get random page
expired on customers site
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028903#comment-13028903 ]
Martin Grigorov commented on WICKET-3667:
-----------------------------------------
I just committed an improvement.
Can you try latest -SNAPSHOT and send feedback ?
> 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
> Attachments: heartbeatProblem.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
[jira] [Commented] (WICKET-3667) Once in a while we get random page
expired on customers site
Posted by "Pedro Santos (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030305#comment-13030305 ]
Pedro Santos commented on WICKET-3667:
--------------------------------------
I can't reproduce the problem here unless I decrease the DiskDataStore maxSizePerPageSession. The only potential problem I see are distinct threads storing distinct pages without the happens-before relationship. It can cause indexPointer variable getting incremented twice and read by those threads only after it get double incremented. In this scenario the PageWindowManager would map only one of those pages to the new index, and in the next call the not mapped page will cause the page expired exception.
PageAccessSynchronizer synchronize threads by page id, but different threads can use the same PageWindowManager to map different pages.
Is my concern valid? I'm trying to imaging what generated the reported problem since I could not reproduce it here.
> 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
>
>
> 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
[jira] [Commented] (WICKET-3667) Once in a while we get random page
expired on customers site
Posted by "Mauricio Lopez-Soto (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13040402#comment-13040402 ]
Mauricio Lopez-Soto commented on WICKET-3667:
---------------------------------------------
Martin,
Because of some requirements, we can't ping the main window so we will be making the disk store bigger. Looking forward to having IStoreSettings.
Thanks for your help.
Cheers
Mauricio
> 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
[jira] [Commented] (WICKET-3667) Once in a while we get random page
expired on customers site
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038010#comment-13038010 ]
Martin Grigorov commented on WICKET-3667:
-----------------------------------------
Any news here ?
Do you experience this issue with RC4.2 ?
> 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
>
>
> 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
[jira] [Commented] (WICKET-3667) Once in a while we get random page
expired on customers site
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13040406#comment-13040406 ]
Martin Grigorov commented on WICKET-3667:
-----------------------------------------
What requirements if it is not secret ?
Because adding AjaxSelfUpdatingTimerBehavior that sends a request back to the page every N seconds should be very light and transparent.
> 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
[jira] [Reopened] (WICKET-3667) Once in a while we get random page
expired on customers site
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov reopened WICKET-3667:
-------------------------------------
It seems I'll have to revert the "improvement" for your ticket (WICKET-3667).
https://issues.apache.org/jira/browse/WICKET-3676 is broken because of
this change.
AFAIK Wicket should not store the page for Ajax requests (this is what
I know from the other devs) but apparently this is not quite true.
I tried the app in 3676 in latest 1.4.x and it works fine. So I
debugged it and it seems Wicket 1.4.x actually stores the page after
Ajax request.
So now I'm a confused what to do.
@Other devs: any advises ?
> 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
> Fix For: 1.5-RC4
>
> Attachments: heartbeatProblem.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
[jira] [Assigned] (WICKET-3667) Once in a while we get random page
expired on customers site
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov reassigned WICKET-3667:
---------------------------------------
Assignee: Martin Grigorov
> 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
>
>
> 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
[jira] [Commented] (WICKET-3667) Once in a while we get random page
expired on customers site
Posted by "Nino Martinez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028877#comment-13028877 ]
Nino Martinez commented on WICKET-3667:
---------------------------------------
ok so what you essentially are saying are that I can affect total, by changing jvm settings right? but why are totalt different from max then?
> 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
> Attachments: heartbeatProblem.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
[jira] [Commented] (WICKET-3667) Once in a while we get random page
expired on customers site
Posted by "Nino Martinez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030312#comment-13030312 ]
Nino Martinez commented on WICKET-3667:
---------------------------------------
Im not sure either. But I can reproduce it on my laptop using the quickstart... And our product are awaiting the fix to function properly.. Otherwise the customer can only have one or two open browser instances.. And that is very bad :(
So what do you need from me?
> 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
>
>
> 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
[jira] [Commented] (WICKET-3667) Once in a while we get random page
expired on customers site
Posted by "Mauricio Lopez-Soto (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038926#comment-13038926 ]
Mauricio Lopez-Soto commented on WICKET-3667:
---------------------------------------------
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
>
>
> 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
[jira] [Commented] (WICKET-3667) Once in a while we get random page
expired on customers site
Posted by "Mauricio Lopez-Soto (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13046013#comment-13046013 ]
Mauricio Lopez-Soto commented on WICKET-3667:
---------------------------------------------
As I said in a previous comment, the workaround that we are using is changing the default values of the DefaultPageManagerProvider. We set the getCacheSize() and getMaxSizePerSession() to 0. What I noticed is that by having getMaxSizePerSession() always returning 0, the PageWindowManager index is always incremented, never goes back to zero. Event though it is working, I was wondering if this might be a problem for long running sessions (several days).
> 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
[jira] [Updated] (WICKET-3667) Once in a while we get random page
expired on customers site
Posted by "Nino Martinez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nino Martinez updated WICKET-3667:
----------------------------------
Attachment: heartbeatProblem.zip
quickstart
> 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
> Attachments: heartbeatProblem.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
[jira] [Commented] (WICKET-3667) Once in a while we get random page
expired on customers site
Posted by "Nino Martinez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028785#comment-13028785 ]
Nino Martinez commented on WICKET-3667:
---------------------------------------
but how do one determine the total, if I can change that it would help..
> 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
> Attachments: heartbeatProblem.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
[jira] [Commented] (WICKET-3667) Once in a while we get random page
expired on customers site
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038399#comment-13038399 ]
Martin Grigorov commented on WICKET-3667:
-----------------------------------------
JIm, your problem seems to be related to wrong Apache configuration. Better ask in the mailing lists of Tomcat.
> 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
>
>
> 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
[jira] [Commented] (WICKET-3667) Once in a while we get random page
expired on customers site
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028765#comment-13028765 ]
Martin Grigorov commented on WICKET-3667:
-----------------------------------------
Not sure how your real application looks like but here is what I think happens in the quickstart:
There is just one page which is stored in the http session. Since Ajax requests don't change page version there are no more versions of that page to be stored. So there is no need to store this page instance in the disk. By creating more tabs you exhaust the free memory and at one point the page is cleaned from the memory because the pages are stored in SoftReferences - see org.apache.wicket.pageStore.DefaultPageStore.SerializedPagesCache.cache. Next Ajax call can't find the page anymore because it is no more in memory (http session) nor in disk (never got there). Thus the page expired exception.
It seems my machine is more powerful than yours because I cannot make it close-to-out-of-memory. I have 4 instances of Firefox each with 10-12 tabs, the counter reached ~6000 and all is fine. I even set -Xms8m and -Xmx8m but the GC is so aggressive that 'used' cannot get equal to 'total' (8M).
You may try to set org.apache.wicket.DefaultPageManagerProvider.getCacheSize() to 0. This way there wont be memory store and the page will be serialized immediately in the disk store. The drawback is that each ajax call will hit the disk.
> 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
> Attachments: heartbeatProblem.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
[jira] [Updated] (WICKET-3667) Once in a while we get random page
expired on customers site
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov updated WICKET-3667:
------------------------------------
Fix Version/s: (was: 1.5-RC4)
> 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
>
>
> 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
[jira] [Commented] (WICKET-3667) Once in a while we get random page
expired on customers site
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13029213#comment-13029213 ]
Martin Grigorov commented on WICKET-3667:
-----------------------------------------
Check the "Subversion commits" tab here in the ticket and decide for yourself.
> 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
>
>
> 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
[jira] [Commented] (WICKET-3667) Once in a while we get random page
expired on customers site
Posted by "Mauricio Lopez-Soto (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13032818#comment-13032818 ]
Mauricio Lopez-Soto commented on WICKET-3667:
---------------------------------------------
We have a problem which we believe is related to the same bug.
We have an application that after the user is authenticated shows a page with two iFrames, where each frame points to a different page, one is map and the other one contains a DataTable. The page has a timer (JavaScript) that refreshes some components of these two pages (AJAX), but not the pages themselves, every 5 seconds. After some time (kind of ramdom, could be one minute, could be 20) the app crashes because of a PageExpiredException.
I hope this helps to pinpoint the problem. Is there anything I can do to get around this bug while the it gets fixed?
> 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
>
>
> 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
[jira] [Resolved] (WICKET-3667) Once in a while we get random page
expired on customers site
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov resolved WICKET-3667.
-------------------------------------
Resolution: Fixed
Fix Version/s: 1.5-RC4
Cool!
Our QA also experienced similar problem but he didn't know how to reproduce it.
Thanks for the quickstart! Hopefully it will solve our problem too.
> 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
> Fix For: 1.5-RC4
>
> Attachments: heartbeatProblem.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
[jira] [Commented] (WICKET-3667) Once in a while we get random page
expired on customers site
Posted by "Nino Martinez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13031196#comment-13031196 ]
Nino Martinez commented on WICKET-3667:
---------------------------------------
Have tried with the latest snapshot today, and are unable to reproduce with the quick start.. However as this is a pretty elusive bug, I'd like to try our app at customers site before closing it..
> 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
>
>
> 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
[jira] [Issue Comment Edited] (WICKET-3667) Once in a while we get
random page expired on customers site
Posted by "Mauricio Lopez-Soto (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13032818#comment-13032818 ]
Mauricio Lopez-Soto edited comment on WICKET-3667 at 5/13/11 4:04 AM:
----------------------------------------------------------------------
We have a problem which we believe is related to the same bug.
We have an application that after the user is authenticated shows a page with two iFrames, where each frame points to a different page, one is map and the other one contains a DataTable. The page has a timer (JavaScript) that refreshes some components of these two pages (AJAX), but not the pages themselves, every 5 seconds. After some time (kind of ramdom, could be one minute, could be 20) the app crashes because of a PageExpiredException.
I hope this helps to pinpoint the problem.
was (Author: mlopezsoto):
We have a problem which we believe is related to the same bug.
We have an application that after the user is authenticated shows a page with two iFrames, where each frame points to a different page, one is map and the other one contains a DataTable. The page has a timer (JavaScript) that refreshes some components of these two pages (AJAX), but not the pages themselves, every 5 seconds. After some time (kind of ramdom, could be one minute, could be 20) the app crashes because of a PageExpiredException.
I hope this helps to pinpoint the problem. Is there anything I can do to get around this bug while the it gets fixed?
> 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
>
>
> 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
[jira] [Commented] (WICKET-3667) Once in a while we get random page
expired on customers site
Posted by "Nino Martinez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13043228#comment-13043228 ]
Nino Martinez commented on WICKET-3667:
---------------------------------------
Thats right in line with what I was experience.
> 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
[jira] [Commented] (WICKET-3667) Once in a while we get random page
expired on customers site
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041007#comment-13041007 ]
Martin Grigorov commented on WICKET-3667:
-----------------------------------------
It was good that I asked :-)
You can use AbstractAjaxTimerBehavior (AjaxSelfUpdatingTimerBehavior) just to "touch" the page which will cause a storing of the current page version in the stores (IPageStore and IDataStore) but you'll not re-render anything, i.e. you wont do anything in onTimer().
public MyPage(PageParameters params) {
super(params);
add(new AbstractAjaxTimerBehavior(Duration.seconds(30) {
protected void onTimer(final AjaxRequestTarget target) {}
});
}
> 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
[jira] [Commented] (WICKET-3667) Once in a while we get random page
expired on customers site
Posted by "Nino Martinez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028754#comment-13028754 ]
Nino Martinez commented on WICKET-3667:
---------------------------------------
I noticed that it only seemed to occur when the total and used memory consumption clashed like the below line:
INFO - DummyRequestLogger - time=2609,event=null,response=null,sessionid=1hz2dq3mc1fxlrru26h4vn19k,sessionsize=662,sessionstart=Wed May 04 16:07:25 CEST 2011,requests=3,totaltime=3171,activerequests=0,maxmem=66M,total=2M,used=2M
> 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
> Attachments: heartbeatProblem.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
[jira] [Commented] (WICKET-3667) Once in a while we get random page
expired on customers site
Posted by "Mauricio Lopez-Soto (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13040996#comment-13040996 ]
Mauricio Lopez-Soto commented on WICKET-3667:
---------------------------------------------
We are using Google maps to show live data. We refresh the markers on the maps every 5 to 20 seconds, but we can't reload the maps very often (we were told to minimize reloading of the map as much as possible, and reloading the page reloads the map as well) because we have a limited number of map views. This is because we bought a Google Maps license that allows for certain number of map views, and going beyond that limit is going to cost us extra.
Maybe there is a way to using AjaxSelfUpdatingTimerBehavior to reload the page but not the maps?
> 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
[jira] [Commented] (WICKET-3667) Once in a while we get random page
expired on customers site
Posted by "Mauricio Lopez-Soto (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13043007#comment-13043007 ]
Mauricio Lopez-Soto commented on WICKET-3667:
---------------------------------------------
Martin,
Using AbstractAjaxTimerBehavior as you suggested does not seem to be working, we are getting the page expired exception. I tried setting the page state to dirty (target.getPage().dirty()) but it did not work either. Maybe I am missing something.
Thanks
Mauricio
> 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
[jira] [Commented] (WICKET-3667) Once in a while we get random page
expired on customers site
Posted by "Jim Larsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038133#comment-13038133 ]
Jim Larsen commented on WICKET-3667:
------------------------------------
I have experienced PageExpiredExceptions in RC4.2 and still on 1.5-SNAPSHOT
I have been struggling to create a quickstart, with no success.
It is somehow related to mounted pages, as I can move my problems by changing the mounted pages.
I have a site that could be illustrated like this.
/homepage (mounted page)
/admin/page1 (mounted as /admin and protected by AuthStrat)
/admin/page2 (protected by AuthStrat)
/login
When I stats my site I end up on homepage, I then by hand enter the url /admin that should take me to page1, but its protected, and i get to the /login, successful login would normally send me to page1
But here is the problem.
In jetty everything works perfect (I get to page 1)
In tomcat without apache in front everything works perfect ( I get to page 1)
But with apache in front of tomcat, I see problems.
Somehow It messes with the session and I am logged in but there is no page to continue to, witch results in that i end up on homepage (but user is logged in on this session (i get links to my admin pages).
Now i click on link to page1 and this is shown, but now it does not matter what i do. I will get an PageExpiredException from the page)
Using page2 will not result in PageExpired (that page is protected in the same way as page 1, but was not part of my login)
If I change my mount from page1 to page2, I see same result, but all problems will come on page2 and page1 will work.
Another problem is that if i clik on a link to my homepage, the user is by magic logged out !!
I suspect that the problem is related to session (cant say exactly why, but it appears as if there are 2 sessions involved)
Clicking on my homepage link should load my homepage, but it looks as if it is a cached version (but pages are not cached, to my knowledge, and I have checked to see if all headers are in my response (they are))
But as I wrote, I only see the problems with PageExpired, when having Apache in front of tomcat.
Sorry about this bad description, but as I am not able to create a quickstart, it means I'm not understanding the problem my self.
My problem is not random, as I can reproduce it, but I suspect that it is somehow related.
> 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
>
>
> 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
[jira] [Commented] (WICKET-3667) Once in a while we get random page
expired on customers site
Posted by "Nino Martinez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13029210#comment-13029210 ]
Nino Martinez commented on WICKET-3667:
---------------------------------------
In progress, inital testing on my pc went well. Now rolling out to customers site..
Is the improvement simple, so I could "patch" the RC3 or?
> 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
>
>
> 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
[jira] [Commented] (WICKET-3667) Once in a while we get random page
expired on customers site
Posted by "Nino Martinez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13039031#comment-13039031 ]
Nino Martinez commented on WICKET-3667:
---------------------------------------
Martin, sorry for the delayed answer we are very busy (near the end of a development cycle). We should be able to retest again near the end of next week.
> 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
[jira] [Commented] (WICKET-3667) Once in a while we get random page
expired on customers site
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13040220#comment-13040220 ]
Martin Grigorov commented on WICKET-3667:
-----------------------------------------
Mauricio,
Here is what happens in your quickstart:
DiskDataStore stores the pages in the file system, setMaxSizePerSession(someBytes) configures how big the file can be per session, in bytes. Initially you create the first page, it is stored at position 1 in the file, then you create N new pages which are stored at 2, 3, ..., N. When N*pageSize becomes bigger than someBytes DiskPageStore starts to write any new page from the beginning of the file, i.e. overrides the oldest one.
To solve the problem either ping the main page from time to time as I told you in stackoverflow.com before, or make the disk store bigger. I think the first option is better.
In trunk I introduced IStoreSettings which can be used to tweak the settings for the default impls of IPageStore, IDataStore and IPageManager. You'll need to touch your app when upgrading to next version but I believe it is for good.
> 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
[jira] [Commented] (WICKET-3667) Once in a while we get random page
expired on customers site
Posted by "Nino Martinez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13029227#comment-13029227 ]
Nino Martinez commented on WICKET-3667:
---------------------------------------
Our testing on customers site shows it is fixed :) Thanks ALOT Martin for helping out..
> 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
>
>
> 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
[jira] [Updated] (WICKET-3667) Once in a while we get random page
expired on customers site
Posted by "Mauricio Lopez-Soto (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mauricio Lopez-Soto updated WICKET-3667:
----------------------------------------
Comment: was deleted
(was: -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.)
> 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
[jira] [Resolved] (WICKET-3667) Once in a while we get random page
expired on customers site
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov resolved WICKET-3667.
-------------------------------------
Resolution: Not A Problem
Closing as not a problem until proven otherwise.
> 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
[jira] [Commented] (WICKET-3667) Once in a while we get random page
expired on customers site
Posted by "Mauricio Lopez-Soto (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041168#comment-13041168 ]
Mauricio Lopez-Soto commented on WICKET-3667:
---------------------------------------------
Martin,
This sounds like a much better way of solving this.
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
[jira] [Commented] (WICKET-3667) Once in a while we get random page
expired on customers site
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028780#comment-13028780 ]
Martin Grigorov commented on WICKET-3667:
-----------------------------------------
I am not correct. The first version of the page is actually stored in the disk store:
org.apache.wicket.pageStore.DefaultPageStore.storePage(String, IManageablePage) does that.
Will investigate further...
> 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
> Attachments: heartbeatProblem.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