Unfortunately issue still exists, even after we moved to 2.2. here is my original post.
http://dev.day.com/discussion-groups/content/lists/jackrabbit-users/2010-12/2010-12-29_Concurrency_issues_after_upgrading_to_2_2_from_1_6_shailesh_mangal.html In our use case, we allow bulk operations where multiple users add nodes to the same parent. Each user request runs on its own thread and doesnt share the session (common authentication credentials though). We are very hard pressed to fix this issue and considering all alternatives at this point. Any help is highly appreciated. -Shailesh ________________________________ From: Jukka Zitting <[email protected]> To: [email protected] Sent: Wed, January 5, 2011 8:32:07 AM Subject: Re: Jackrabbit 1.6.4 locking issue Hi, On Wed, Jan 5, 2011 at 5:19 PM, Raj <[email protected]> wrote: > Any pointers would be helpful. This seems like one deadlock scenario I fixed as a part of JCR-2699 [1]. Can you check if the problem still occurs with the latest 2.x releases? See also JCR-2791 [2] for some relevant followup discussion. [1] https://issues.apache.org/jira/browse/JCR-2699 [2] https://issues.apache.org/jira/browse/JCR-2791 BR, Jukka Zitting
