[
https://issues.apache.org/jira/browse/WICKET-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hielke Hoeve updated WICKET-2722:
---------------------------------
Affects Version/s: 1.4.9
1.4.8
1.4.7
It is impossible to create a subclass or a sibling class for this problem
because the interface is hooked to the RequestLogger (why create an interface
if its hooked to some impl?). I am uncertain as to how this problem should be
tackled, is there a valid way to see if the user is logging out?
> RequestCycle.detach() recreates SessionData after logout
> --------------------------------------------------------
>
> Key: WICKET-2722
> URL: https://issues.apache.org/jira/browse/WICKET-2722
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.4.6, 1.4.7, 1.4.8, 1.4.9
> Environment: Wicket 1.4.6, Spring 2.5.6, Hibernate 3.3.1-GA, AspectJ
> 1.6.8, Eclipse 3.5.2, Windows 7 32bit
> Reporter: Hielke Hoeve
> Priority: Minor
>
> After every page request the RequestCycle asks the RequestLogger (if any) to
> write the time taken etc to the logger (using the SessionData of the current
> Session). If none exists then a new SessionData is created (RequestLogger
> line 250). However when a user logs out the SessionData is destroyed, but the
> page still has to detach and thus creates a new SessionData entity.
> When we lookup the live sessions and peak sessions from RequestLogger,
> the two numbers are (nearly) always the same. Which is wrong when all users
> have logged out or closed their browser (no difference there).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
