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] Commented: (JCR-641) can't add lock token to session after 3 login/logout
Date Wed, 29 Nov 2006 14:54:22 GMT
    [ http://issues.apache.org/jira/browse/JCR-641?page=comments#action_12454333 ] 
Stefan Guggisberg commented on JCR-641:

pseudo code for reproducing the issue:

- sessionA locks a node and retrieves the lock token
- sessionA logs out (or lock token is removed from sessionA)

- lock token is transfered to sessionB
- sessionB logs out (or lock token is removed from sessionB)

- lock token is transfered to sessionC
- sessionC tries to unlock the node => LockException

> can't add lock token to session after 3 login/logout
> ----------------------------------------------------
>                 Key: JCR-641
>                 URL: http://issues.apache.org/jira/browse/JCR-641
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: locks
>    Affects Versions: 1.1
>         Environment: Linux Ubuntu Dapper
>            Reporter: Paco Avila
>         Assigned To: Stefan Guggisberg
>            Priority: Critical
>         Attachments: DummyLockToken.java, DummyLockToken.log, repository2.xml
> I login and lock a file and logout. Perfoms a new login and add the previous lock token
to the current session because I want to unlock this file. This works fine. But if I do a
new logout/login I can't unlock the file (the file is locked). It is best understanded looking
at the test case.

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


View raw message