jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Guggisberg (JIRA)" <j...@apache.org>
Subject [jira] Closed: (JCR-125) Repository holds onto Session instance after logout
Date Tue, 24 May 2005 12:40:56 GMT
     [ 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


Mime
View raw message