Would be interesting to see if only locking around the "login" fixes it, meaning a 'viable workaround' would one Repository per thread? If you have the source, you can just put a breakpoint on that line and see what lead to it happening pretty easily. Maybe not root cause, but you can know much more than just an error message. If JCR is truly failing on this test case it is a VERY serious problem. Worth looking into becasue proper locking behavior is absolutely a critical function.
Best regards, Clay Ferguson [email protected] On Tue, Apr 12, 2016 at 5:30 PM, arshi <[email protected]> wrote: > i tried the ticket : > https://issues.apache.org/jira/browse/JCR-2579 > https://issues.apache.org/jira/browse/JCR-2598 > > Still no luck , Can someone help me to resolve this issue............. > > > > > -- > View this message in context: > http://jackrabbit.510166.n4.nabble.com/javax-jcr-RepositoryException-Failed-to-update-after-5-attempts-giving-up-d74d7d28-f0c2-473a-ac41-9dy-tp4663932p4663933.html > Sent from the Jackrabbit - Users mailing list archive at Nabble.com. >
