By the way, another file created some time ago is working with locking and unlocking via DAV Explorer. When this file is locked, it has lock token value and correct DAV Explorer timeout but none jcr:lockOwner or jcr:lockIsDeep in server. The log for unlocking this file shows "*WARN * LockManagerImpl: Bad lock token: Bad check digit. (LockManagerImpl.java, line 811)", however locking/unlocking works actually works on this file.
It seems different files on same jackrabbit server work differently. The file which has perfect log is not correctly locked but the file which has warning in log is correctly locked. I'm really lost... Does it have something to do with configuration or..? ________________________________ From: Xiaojie Shen [mailto:[email protected]] Sent: den 29 juli 2010 21:29 To: [email protected] Subject: jackrabbit problem to set locktoken and unlock Hi all I use DAV Explorer to do exclusive lock on a file in jackrabbit repository, the file is locked but lock token is empty and timeout is "Second-2147483" (according to DAV Explorer document, the lock it requests is 86,400 seconds or 1 day). In addition, I see jcr:lockOwner and jcr:lockIsDeep in jackrabbit server. Then I do unlock via DAV Explorer to the same file. Though the DAV Explorer lock icon is gone, the lock properties are still the same and actually the file is still locked. Any idea why jackrabbit sets empty lock token and the extreme long timeout and why it can't unlock? BR Xiaojie
