Ivan, I am experiencing this condition as well, using OrientDB 2.0.5. Is this known, or is it just inexperience?
In my Java code I am starting with a Json data record, storing it, then traversing some of the properties in the record I just stored, pulling out foreign key IDs, and creating edges to other documents I create based on the foreign key ID values in the data. Sometimes it works fine, but most time I get a deadlock. Any suggestions? Patrick On Thursday, March 5, 2015 at 6:41:11 AM UTC-7, Ivan Jovanovic wrote: > > Thank you very much, Emanuele, for your reply and the clarification! > > I am aware that technically this is not a deadlock, but practically it is, > since the application is waiting for a lock to be released and it never > gets released. I know that 'never' is a powerful word to be used here, but > the thread was waiting 20 minutes for the lock before I decided to stop the > application, so I can assume that it would wait even more. > > How can I overcome this problem (that I still experience, from time to > time)? > > Cheers, > Ivan > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to orient-database+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
