Troubleshooting

• JVM SIGSEGV crash

LMDB Java API maps well to the LMDB C API. So it's necessary to understand the LMDB C API in order to troubleshoot the cause of a SIGSEGV, which happens in corner cases that may seem like bug. The official docs are excellent and very precise. Read it. Many times. Applicable to lmdbjni in every sense.

• Sporadic exceptions "MDB_BAD_RSLOT: Invalid reuse of reader locktable slot"

Set Constants.NOTLS option on Env.open().