-
Notifications
You must be signed in to change notification settings - Fork 831
Deadlock in BinaryLogClient? #321
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
Comments
PS: I was able to repro by setting the keep alive interval to 1 and the heartbeat interval to 10... |
Thanks, Andy! Fix included in 0.21.0. |
This reverts commit 4680cb8 (caused shyiko#321).
@shyiko Hello - I was wondering if you might be able to give some context on what specifically about the two commits in 0.21.0 was intended to fix the deadlock issue brought up here. I was attempting to add the fix in to the maintained Osheroff fork of this library but the two commits contain a number of unrelated changes too. Any guidance you could provide would be very appreciated! |
I think there may be a deadlock in the code when a term is received. Here is my stack trace
Just to keep things simple I'll use:
K=keepAliveThreadExecutorLock
C=connectLock
In the below
Here's the abridged stack. Am I missing something?
The text was updated successfully, but these errors were encountered: