[
https://issues.apache.org/jira/browse/JCR-672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481921
]
Jukka Zitting commented on JCR-672:
---
Is there anything a non-Jackrabbit-developer can do to help?
I'm afraid
[
https://issues.apache.org/jira/browse/JCR-672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481956
]
Sebastian Redl commented on JCR-672:
Reporting all known deadlock occurrences with as much detail as possible
[
https://issues.apache.org/jira/browse/JCR-672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481867
]
Sebastian Redl commented on JCR-672:
Is there anything a non-Jackrabbit-developer can do to help? This bug is
[
http://issues.apache.org/jira/browse/JCR-672?page=comments#action_12457666 ]
Tobias Bocanegra commented on JCR-672:
--
could have been introduced by JCR-546.
Deadlock on concurrent save/checkin operations possible
[
http://issues.apache.org/jira/browse/JCR-672?page=comments#action_12457695 ]
Jukka Zitting commented on JCR-672:
---
The proper solution to this issue would probably be to acquire the
SharedItemStateManager read lock for the entire checkin
[
http://issues.apache.org/jira/browse/JCR-672?page=comments#action_12457693 ]
Jukka Zitting commented on JCR-672:
---
You marked this as occurring in 1.1? If correct, then it shouldn't be caused by
JCR-546, since it's not included in either 1.1
[
http://issues.apache.org/jira/browse/JCR-672?page=comments#action_12457707 ]
Przemo Pakulski commented on JCR-672:
-
It is occuring in trunk.
I have checked 1.1 by accident then I couldn't change this ...
Deadlock on concurrent
