[
https://issues.apache.org/jira/browse/WICKET-2291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12769632#action_12769632
]
Martin Grigorov commented on WICKET-2291:
-----------------------------------------
I think this ticket is INVALID.
As Johan inclined in the mail thread you incorrectly use invalidate methods.
Session.invalide() schedules the session as invalid after the end of the
current request (it's the very first sentence in the method's comment).
Session.invalidateNow() invalidates immediately.
> 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
> 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.
