You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Johan Compagner (JIRA)" <ji...@apache.org> on 2007/09/11 09:39:32 UTC

[jira] Commented: (WICKET-953) Session invalidateNow() does not immediate remove the session from disk

    [ https://issues.apache.org/jira/browse/WICKET-953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526378 ] 

Johan Compagner commented on WICKET-953:
----------------------------------------

i think what happens is that invalidateNow invalidates the session immediately and then
the file is deleted  for that session. But then after the request the current page that is touched is saved
again so the file is created again for that session.

invalidateNow is a call that shouldn't be called for 99% of the times that you want to invalidate a session
i think even the current behavior is wrong if we call invalidateNow we should create a new http session somehow 
and start working with that one (maybe this already happens somehow but we still use the old id)

> Session invalidateNow() does not immediate remove the session from disk
> -----------------------------------------------------------------------
>
>                 Key: WICKET-953
>                 URL: https://issues.apache.org/jira/browse/WICKET-953
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.3.0-beta3
>            Reporter: chris lintz
>            Priority: Minor
>
> The only way i can see the session removed immediately is if Session invalidate() is called.  invalidateNow() does not remove the session from disk as expected.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.