[
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
