Hi, On Wed, Jan 5, 2011 at 9:16 PM, shailesh mangal <[email protected]> wrote: > Unfortunately issue still exists, even after we moved to 2.2.
Do you still see this problem in your deployment? I found a somewhat similar (though not exactly the same) deadlock scenario with the latest trunk, see JCR-890 [1]. It would be great if you could check if the stacktraces match your case. I don't believe the original deadlock case described for 1.6.4 can occur anymore in 2.2. [1] https://issues.apache.org/jira/browse/JCR-2890 BR, Jukka Zitting
