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
There is no deadlock, the main tread is waiting on the lock because
there is the service thread( called Asynch Client) that is reading the
channel, as soon as an answer come back the service thread will read it,
see that is not something that it need to handle an let the channel
control to the
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
