Details
-
Bug
-
Status: Closed
-
Normal
-
Resolution: Cannot Reproduce
-
None
-
None
-
None
Description
The thread that attempts to set the lock seems to stall and then an exception is thrown (one of several that all suggest concurrent access to the session that is used to set the lock) or eventually succeeds but then the subsequent attempt to start a keep-alive fails because the lock has timed out in the meantime.
Attachments
Issue Links
- relates to
-
REPO-1381 Concurrent session access in Jackrabbit's LockManager timeout handler
- Closed