Skip to content
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

Handle read deadlocks #1

Merged
merged 6 commits into from
Oct 2, 2013
Merged

Handle read deadlocks #1

merged 6 commits into from
Oct 2, 2013

Conversation

kmorey
Copy link

@kmorey kmorey commented Oct 2, 2013

Updated to latest upstream, reverted our last bug fix that is now unnecessary and add some handling for deadlocks when server and worker are both trying to read

David Shrewsbury and others added 6 commits August 7, 2013 12:07
SSL has in internal read buffer that needs to be drained. Since
we, by default, read in 4K chunks, anything larger would have left
data to be read that may not have been processed properly.

Also, we need to handle SSL_ERROR_WANT_READ and SSL_ERROR_WANT_WRITE
exceptions around the recv() and send() calls, otherwise we would
think we are disconnected and cause all sorts of problems.
When using multiple job servers, some connections may not yet be
established (not been chosen yet), so their socket is still invalid.
This would cause poller.register() to throw an exception.
Address some SSL handling issues.
@chrisvaughn
Copy link
Member

👍

chrisvaughn added a commit that referenced this pull request Oct 2, 2013
@chrisvaughn chrisvaughn merged commit 0fbcf73 into master Oct 2, 2013
@chrisvaughn chrisvaughn deleted the km/read_deadlocks branch October 2, 2013 18:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants