[
https://issues.apache.org/jira/browse/JCR-2855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-2855:
-------------------------------
Component/s: jackrabbit-core
You tested this with 2.1.3, right? This seems related to JCR-2820, but is
probably a slightly different problem since JCR-2820 is already fixed in 2.1.3.
Can you still reproduce the problem with 2.2.x? If you can, please post a
thread dump to make it easier to analyze the problem.
> Writers blocked forever when waiting on update operations
> -----------------------------------------------------------
>
> Key: JCR-2855
> URL: https://issues.apache.org/jira/browse/JCR-2855
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 2.1.3
> Reporter: Yoav Landman
>
> Thread 1 calls Session.save() and has a write lock.
> Thread 2 is in XA prepare() and is waiting on thread 1 in
> FineGrainedISMLocking.acquireWriteLock().
> Thread 1's save calls SharedItemStateManager.Update#end() and performs a
> write-lock downgrade to a read-lock, then (at the end of Update#end()) it
> calls readLock.release(). FineGrainedISMLocking.ReadLockImpl#release thinks
> activeWriterId is of the current transation and does not notify any writers
> (activeWriterId is not being reset on downgrade in what seems to be a related
> to JCR-2753).
> Thread 1 waits forever.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
