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

Igor Vaynberg resolved WICKET-2722.
-----------------------------------

    Resolution: Invalid
      Assignee: Igor Vaynberg  (was: Peter Ertl)

i dont think the assumption that peak always == live is correct looking at the 
code. peak is the max(live). even if the user logs out and redirected to login 
page immediately after - unless they log in their session will timeout - and at 
that point live sessions count will decreated, but peak will not. so while live 
is not "instanteneous' if you look at it from the application lifecycle's point 
of view, it does eventually catch up when the servlet container drops the 
session.

> 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, 1.4.10, 1.4.11
>         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
>            Assignee: Igor Vaynberg
>            Priority: Minor
>              Labels: login, logout, requestcycle, requestlogger, session, 
> sessiondata
>         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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to