Stalls using lmdbjava about lmdbjava HOT 4 CLOSED

Your stack trace is from the primordial thread created by the OS for the java process. Ever since Java 6, the primordial thread loads the VM, starts a thread to run the VM, and goes to sleep waiting for the VM main thread to exit. A stack trace of the primordial thread is going to be the same across all java processes and has no reference to any code running inside the VM.

Here is the code for JLI_Launch

from lmdbjava.

Was this ever resolved?

Have you tried to run the Verifier?

from lmdbjava.

We've moved on from trying lmdb due to the lack of parallelism in general, which we require. I'm going to close the issue for that reason, but we never resolved the actual stall. Thank you!

from lmdbjava.

Thanks for the follow up. The wiki has some pages that may have helped. The concurrency page in particular is worth a look for anyone who finds this issue. It may have been for example the LMDB requirement that there be only one write transaction at a time. Subsequent attempts to obtain a write transaction when there is already one in flight will result in a blocking wait.

from lmdbjava.