[
https://issues.apache.org/jira/browse/WICKET-4078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114309#comment-13114309
]
Martin Grigorov commented on WICKET-4078:
-----------------------------------------
This sounds like a problem with the setup of your application.
For some reason the jsession cookie/url-piece is not delivered back to
recognize the previously created session and that's why a new one is being
created.
Without a quickstart and a step by step description of the way you setup your
application it will be very hard to tell you what is wrong.
All I can say right now is that no new sessions are created in the application
I'm working on. The difference is that we use Tomcat 6.x instead of JBoss.
Try your app in Tomcat/Jetty/Glassfish and see whether there is a difference.
> 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
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
