This repository has been archived by the owner on Jun 1, 2021. It is now read-only.
LevelDB event log crashes JVM on shutdown frequently #234
Comments
jrudolph
added a commit
to jrudolph/eventuate
that referenced
this issue
Mar 14, 2016
Previously, creating an iterator and tracking wasn't an atomic operation resulting in iterator operations being run after the db had been closed. This resulted in all kinds of crashes because of illegal native state during the shutdown procedure.
jrudolph
added a commit
to jrudolph/eventuate
that referenced
this issue
Mar 17, 2016
Previously, creating an iterator and tracking wasn't an atomic operation resulting in iterator operations being run after the db had been closed. This resulted in all kinds of crashes because of illegal native state during the shutdown procedure.
krasserm
added a commit
that referenced
this issue
Mar 19, 2016
- Use iterators in child actors and rely on Akka to first stop these child actors before stopping the parent event log actor that shuts down LevelDB. - fixes #234
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
There's already PR #231 which will fix this, I'm just adding this here for reference. Update: this is now fixed by #239.
This is because leveldb iterators may still be in use when native data structures are decommissioned by the
leveldb.close()call (despite the current iterator tracking code).The text was updated successfully, but these errors were encountered: