-
Notifications
You must be signed in to change notification settings - Fork 872
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DeadLock when saving an Object #7172
Comments
@sbespalov could you provide full thread dump? We can not detect deadlock by a single thread. |
@sbespalov why do you think there is deadlock there could you provide me your reasoning? |
@Laa, because application hangs here |
@sbespalov so does thread which you pointed hang there forever? I mean if your test or task is finished and a database is idle you see such hanging thread, do not you? |
@tglman could you look at this ? |
@Laa, It's an UnitTest and it has only one thread |
hi @sbespalov, from what i see the client is just waiting for the server to answer, could you take the thread dump of the server ? or anyway what's the status of the server when you run the specific test case ? Just as a info, the thread is waiting on a lock because there is another thread named as "Asynch Client" getting the data from the network for him. Regards |
@tglman, hi Client and Server running under same JVM, so dump above must also contains Server threads too. |
Hi, I see, well so this thread:
it seems to be the one that is handling the request and is not blocked, so i don't think there is a deadlock, can you send us the test case or "cleared version" of it so we can check it? Regards |
"cleared version" can take some time, I will try to reproduce it separately if needed |
hi @sbespalov, yes i'll try that. Regards |
hi @sbespalov, Regards |
Oh, I am very sorry for that.
|
Just for information |
hi @sbespalov, I reproduced it, is not a deadlock but something is wrong in there, checking. Regards |
Great! |
hi @tglman |
hi @sbespalov, I figure out the source of the problem, and is in the Object Database layer, I'm trying to write a test case that reproduce it in a determistic way and fix it. Regards |
@tglman |
hi @sbespalov, found the root cause, done the test case for the root cause and fixed, i double checked also with your test case and it work correctly, it will be released in 2.2.18, if you want you can try it out in 2.2.18-SNAPSHOT. Closing this. Regards |
@tglman : Many thanks for helping us with this! :) |
Many thanks guys! |
I'm experiencing the same problem as @sbespalov did, even on version 2.2.20. I am using the vertx framework along with orientdb. I get this error only when saving a second entity (different cluster/class but same database) the first save goes through fine. I'm not sure if the first save locks the db. I have included my stacktrace below. I would appreciate any help on this. I have been struggling for hours: May 19, 2017 2:59:37 PM io.vertx.core.impl.BlockedThreadChecker |
@metapp could you send us complete stack trace as separate gist? |
OrientDB Version: 2.2.16
Java Version: 1.8.0_65
OS: Ubuntu 16.04
Please help to resolve it.
Stack:
The text was updated successfully, but these errors were encountered: