[
https://issues.apache.org/jira/browse/WICKET-2291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Juergen Donnerstag resolved WICKET-2291.
----------------------------------------
Resolution: Invalid
Assignee: Juergen Donnerstag
invalideNow() => invalidate the session immediately. This usually not what you
want. invalidate() will invalidate the session when the request has been
completed.
> Session.invalidateNow() makes RequestLogger to recreate invalidated session
> ---------------------------------------------------------------------------
>
> Key: WICKET-2291
> URL: https://issues.apache.org/jira/browse/WICKET-2291
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.6
> Reporter: Taneli Korri
> Assignee: Juergen Donnerstag
> Priority: Minor
>
> When RequestLogger is enabled and a session is invalidated with
> Session.invalidateNow(), the execution order goes the wrong way. The session
> is removed from RequestLogger.liveSessions before the request is logged,
> which leads to RequestLogger recreating the invalidated session and adding it
> back to the RequestLogger.liveSessions.
> This leads to RequestLogger.getLiveSessions() returning bogus sessions, when
> using Session.invalidate() the problem doesn't exist.
> More info:
> http://www.nabble.com/RequestLogger-and-session-invalidation-to23742528.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
