Be aware that we have another thread that read on the same channel for
handle the push request, that main thread is parked there waiting that
the Async client thread get the data from the network, understand that
it's not is data, an give it back to the main thread.
so no deadlock there ;)
On 30/03/15 21:02, Patrick Hoeffel wrote:
<https://lh3.googleusercontent.com/-ebTSvLLuih4/VRmrhCh1nCI/AAAAAAAAQ3c/JYGQAngQ8dg/s1600/OrientDB%2BDeadlock.PNG>
OrientDB 2.0.5 on Windows Server 2012, client connecting from Win 7 Pro
I have a Java class that is inserting a vertex and then adding
outbound edges. I'm doing queries to figure out what intermediate data
needs to also be created in order for my edges to be built properly,
but something is causing a deadlock, and I can only get it to clear by
restarting OrientDB. Here is the stack trace from Eclipse when this
happens:
If anyone has seen this before, please let me know.
Thanks,
Patrick
--
---
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 [email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
---
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
