You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Andrei Badea (JIRA)" <ji...@apache.org> on 2013/10/30 18:39:39 UTC
[jira] [Created] (WICKET-5402) NullPointerException when logging
out
Andrei Badea created WICKET-5402:
------------------------------------
Summary: NullPointerException when logging out
Key: WICKET-5402
URL: https://issues.apache.org/jira/browse/WICKET-5402
Project: Wicket
Issue Type: Bug
Components: wicket-atmosphere
Affects Versions: 6.8.0
Reporter: Andrei Badea
Assignee: Emond Papegaaij
We get the attached NPE when a user logs out.
Apparently what happens is that there are multiple concurrent requests to one session: one "regular" request and a logout request. The logout request calls Session.get().invalidate(), so the session is invalidated at the end of the request. If this happens when "regular" request is already past the authentication check, it will retrieve the session with a now-invalid cookie, resulting in the creation of a new Session object with a null id. This is then put in a PageKey object for an EventBus subscription. When another, unrelated user logs out, EventBus iterates all PageKey-s and chokes on the one that has a null sessionId.
--
This message was sent by Atlassian JIRA
(v6.1#6144)