[ 
https://issues.apache.org/jira/browse/WICKET-4078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117674#comment-13117674
 ] 

lucius commented on WICKET-4078:
--------------------------------

I started debugging it.  
org.apache.wicket.Application.fetchCreateAndSetSession(RequestCycle) is called 
2-3 times everytime I click a link.  First time the session comes back fine 
when SessStore.lookup() is called, then the second or 3rd time will get a null, 
and it goes and creates a new one.
                
> 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
>         Environment: Wicket 1.5.0 running on Jboss 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

        

Reply via email to