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] Resolved: (JCR-441) Session logout doesn't release locks acquired using addLockToken
Date Thu, 30 Nov 2006 14:55:25 GMT
     [ http://issues.apache.org/jira/browse/JCR-441?page=all ]

Stefan Guggisberg resolved JCR-441.
-----------------------------------

    Fix Version/s: 1.2
       Resolution: Fixed
         Assignee: Stefan Guggisberg

fixed in svn r480587 

rod, thanks for this excellent bug report and patch. ... and my excuses that it took so long.
this issue somehow managed to escape my radar  :(

> Session logout doesn't release locks acquired using addLockToken
> ----------------------------------------------------------------
>
>                 Key: JCR-441
>                 URL: http://issues.apache.org/jira/browse/JCR-441
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: locks
>    Affects Versions: 1.0, 1.0.1, 0.9
>         Environment: Windows XP, Jackrabbit 1.0
>            Reporter: Rod Mackenzie
>         Assigned To: Stefan Guggisberg
>             Fix For: 1.2
>
>         Attachments: lock.patch, LockTest.java.patch
>
>
> Session.addLockToken doesn't register locks with the session so when logout is called
they are not released. Locks acquired this way maintain a reference to the Session after logout
and new sessions attempting to acquire the locks will fail.

-- 
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