Hi Matias, please send questions like that to the google group. A deadlock appears when it is about to acquire two locks in reverse order.
What you see is probably just a lock that is not released because the transaction which created it was not closed and is still running? You can check via JMX if there is still an ongoing open transaction and open locks. Also when you take a thread-dump you see what lock (incl. node-id) the thread is waiting for. Cheers, Michael On Fri, Mar 27, 2015 at 4:07 PM, Matias Burak <[email protected]> wrote: > Hi Michael, sorry I bother you again with another problem. > > Is it possible that Neo4j doesn’t realize that it’s in a deadlock? I’m > using an old version of the db (1.9) and when running several transactions > on different threads against the db sometimes the threads get locked and > never are released and I don’t see an exception, they are just stuck on > deadlockGuardedWait(). > I expect deadlocks and I built a retry feature to try again, but I’m not > getting any exceptions :( (sometimes I am) > Any idea? > > Thanks, > MAtias. > > > -- You received this message because you are subscribed to the Google Groups "Neo4j" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
