[
https://issues.apache.org/jira/browse/WICKET-4078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117789#comment-13117789
]
lucius edited comment on WICKET-4078 at 9/30/11 12:41 AM:
----------------------------------------------------------
Ok, here's the findings from debugging the server while hitting it from a
remote browser.
fetchCreateAndSetSession() calls
getSessionStore().lookup(requestCycle.getRequest());
everytime I click a link such as
http://pocketrunway.com/ANTMWeb/model/reneroxanne
fetchCreateAndSetSession() will be called 2-3 times.
each time I introspect the value of requestCycle.getRequest()
first time the toString if getRequest() will be a [GET
/ANTMWeb/model/reneroxanne] so the lookup which uses the key returns a session
second time the toString if getRequest() will be a [GET
/ANTMWeb/model/reneroxanne] so the lookup which uses the key returns a session
again
However if there is a third time(third time occurs intermittently but will
happen if you click enough times 1.5.0 happens a lot more than 1.5.1), the
third time the toString if getRequest() will be a [GET
/ANTMWeb/model/reneroxanne?5] or some number that wicket appended. Now it will
return me a null and a new session is created!
I hope this will help fix the bug?
Again I have to stress that this will never happen if you are doing it on
localhost or with real low latency.
was (Author: nepoez):
Ok, here's the findings from debugging the server while hitting it from a
remote browser.
fetchCreateAndSetSession() calls
getSessionStore().lookup(requestCycle.getRequest());
everytime I click a link such as pocketrunway.com/ANTMWeb/model/reneroxanne
fetchCreateAndSetSession() will be called 2-3 times.
each time I introspect the value of requestCycle.getRequest()
first time the toString if getRequest() will be a [GET
/ANTMWeb/model/reneroxanne] so the lookup which uses the key returns a session
second time the toString if getRequest() will be a [GET
/ANTMWeb/model/reneroxanne] so the lookup which uses the key returns a session
again
However if there is a third time(third time occurs intermittently but will
happen if you click enough times 1.5.0 happens a lot more than 1.5.1), the
third time the toString if getRequest() will be a [GET
/ANTMWeb/model/reneroxanne?5] or some number that wicket appended. Now it will
return me a null and a new session is created!
I hope this will help fix the bug?
Again I have to stress that this will never happen if you are doing it on
localhost or with real low latency.
> WebApplication.newSession() being called for almost all requests within 1
> actual session
> ----------------------------------------------------------------------------------------
>
> Key: WICKET-4078
> URL: https://issues.apache.org/jira/browse/WICKET-4078
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5.0, 1.5.1
> Environment: Wicket 1.5.1 running on jetty 7.5.1 in Ubuntu
> Reporter: lucius
> Priority: Critical
> Labels: memory_leak, session
> Attachments: WicketApplication.java
>
>
> IMPORTANT: This will NOT happen if you are testing it on a local machine or
> within the LAN. It only happens if you are connecting through the net,
> perhaps it requires latency to reproduce. I'm 100% certain of it as I've
> been consistently reproducing the same results when I switch b/t LAN and the
> net.
> Steps to reproduce:
> 1.) create a custom session class
> 2.) in WebApplication override newSession to return your custom session class
> 3.) put a logger in the contructor of the custom session
> 4.) with a browser, navigate around the application from an external machine
> and see the log that you put in step 3 print out indications of your custom
> session being created every few clicks.
> This seems to be happening on the redirect where it appends the ?5 after a
> url? I'm not sure.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
