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

Pathological IVORN causes failure to release eventdb lock #34

Closed
jdswinbank opened this Issue Aug 26, 2014 · 1 comment

Comments

Projects
None yet
1 participant
@jdswinbank
Owner

jdswinbank commented Aug 26, 2014

If we create an event with the IVORN ivo://, then the event db check will attempt to create a database at ${eventdb_root}, which is a directory. This will fail, and the event will be rejected, which is fine.

However, there is now an entry called "" in the list of databases. When we try to prune the databases, that will get locked, but the prune fails and the database is never unlocked. Our event validation then seizes up.

@jdswinbank jdswinbank added the Bugs label Aug 26, 2014

@jdswinbank

This comment has been minimized.

Owner

jdswinbank commented Aug 26, 2014

Every time a new event with the broken IVORN is received, we attempt to acquire the lock on the "" database which hasn't been released. That creates a new thread, which sits their waiting forever. Eventually, we use up our thread limit, and can create no new threads, so nothing except the main loop can run -- no validation, no nothing.

jdswinbank pushed a commit that referenced this issue Aug 26, 2014

@jdswinbank jdswinbank closed this Aug 27, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment