You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Rod Mackenzie (JIRA)" <ji...@apache.org> on 2005/05/23 15:46:53 UTC
[jira] Created: (JCR-125) Repository holds onto Session instance after logout
Repository holds onto Session instance after logout
---------------------------------------------------
Key: JCR-125
URL: http://issues.apache.org/jira/browse/JCR-125
Project: Jackrabbit
Type: Bug
Reporter: Rod Mackenzie
After a call to Session.logout the Repository instance's activeSession map still holds a reference to the session. This causes a problem when trying to unlock nodes locked by another session, the addLockToken method rejects the lock token.
Looking at the code in Session.logout, it tries to notify SessionListeners about the logout but Repository, which implements the SessionListener interface and will remove a session on logout, doesn't register with the Session to receive the logout notification.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Assigned: (JCR-125) Repository holds onto Session instance after logout
Posted by "Stefan Guggisberg (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-125?page=all ]
Stefan Guggisberg reassigned JCR-125:
-------------------------------------
Assign To: Stefan Guggisberg
> Repository holds onto Session instance after logout
> ---------------------------------------------------
>
> Key: JCR-125
> URL: http://issues.apache.org/jira/browse/JCR-125
> Project: Jackrabbit
> Type: Bug
> Reporter: Rod Mackenzie
> Assignee: Stefan Guggisberg
>
> After a call to Session.logout the Repository instance's activeSession map still holds a reference to the session. This causes a problem when trying to unlock nodes locked by another session, the addLockToken method rejects the lock token.
> Looking at the code in Session.logout, it tries to notify SessionListeners about the logout but Repository, which implements the SessionListener interface and will remove a session on logout, doesn't register with the Session to receive the logout notification.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (JCR-125) Repository holds onto Session instance after logout
Posted by "Stefan Guggisberg (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-125?page=all ]
Stefan Guggisberg closed JCR-125:
---------------------------------
Resolution: Fixed
fixed in rev. 178159
> Repository holds onto Session instance after logout
> ---------------------------------------------------
>
> Key: JCR-125
> URL: http://issues.apache.org/jira/browse/JCR-125
> Project: Jackrabbit
> Type: Bug
> Reporter: Rod Mackenzie
> Assignee: Stefan Guggisberg
>
> After a call to Session.logout the Repository instance's activeSession map still holds a reference to the session. This causes a problem when trying to unlock nodes locked by another session, the addLockToken method rejects the lock token.
> Looking at the code in Session.logout, it tries to notify SessionListeners about the logout but Repository, which implements the SessionListener interface and will remove a session on logout, doesn't register with the Session to receive the logout notification.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira