Do you want to upgrade your installation to trunk ? Either you can test the patch attached to JCR-1334 against 1.4 branch or i can give you a patch against trunk. If you copy the DefaultISMLocking you must change the locking classname in Repository.xml and all your Workspace.xml files ...
BR, claus -----Ursprüngliche Nachricht----- Von: James Abley [mailto:[EMAIL PROTECTED] Gesendet: Montag, 13. Oktober 2008 12:46 An: users@jackrabbit.apache.org Betreff: Re: Liveness failures in DefaultISMLocking Hi Claus, Thanks for the response. I've come to the same conclusion. I can't yet upgrade to SVN trunk in our production environment, so I'm going to copy DefaultISMLocking and then add logging so that I can see which thread has the lock at any time. Hopefully this will confirm either way. What I can do if it is caused by that; I've not worked that out yet! Cheers, James 2008/10/13 KÖLL Claus <[EMAIL PROTECTED]>: > hi james, > > do you run your code inside a transaction ? > as i can see you run into a deadlock described in JCR-1334 > > its not so easy to reproduce the problem because the lock is bind to the > thread > and if the container uses the same thread for prepare and commit you get no > problems ... > > BR, > Claus > >> Zip attachment was stripped off. Try this: >> >> http://pastebin.com/m7d46791d >> >> The larger thread dump won't go into the paste bin, so shout if you >> think it's worth having. >> >> I saw that 1.4.6 mentioned a problem with XA and deadlocking in this >> area. But since I can't reliably replicate the problem, it's hard to >> tell whether that will fix it. >> >> Cheers, >> >> James >
