[jira] Updated: (WICKET-2722) RequestCycle.detach() recreates SessionData after logout

["Peter Ertl (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WICKET-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Ertl updated WICKET-2722:
-------------------------------

    Attachment: req-logger.patch

This only seems to happen when using Session#invalidateNow() but not on Session#invalidate().

Unless it's absolutely necessary you should always prefer Session#invalidate().

I attached a fix that should fix the problem.

@Hielke: Please test and give feedback once the fix got applied.

> 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
>         Attachments: req-logger.patch
>
>
> 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.