[
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
