Skip to content

Increase default connection timeout #107

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

Merged
merged 2 commits into from
Jan 17, 2014
Merged

Conversation

rdiomar
Copy link
Collaborator

@rdiomar rdiomar commented Jan 16, 2014

This fixes the default behavior, which used to cause a socket timeout when waiting for 10 seconds for a message to be produced. See #104 (comment)

This fixes the default behavior, which used to cause a socket timeout
when waiting for 10 seconds for a message to be produced.
@mrtheb
Copy link
Collaborator

mrtheb commented Jan 16, 2014

A sensible default (60sec) would make more sense than blocking forever to me, no?

@rdiomar
Copy link
Collaborator Author

rdiomar commented Jan 16, 2014

You're probably right.. It should at least be more than the consumer's ITER_TIMEOUT_SECONDS of 60 though. How about 120?

@mrtheb
Copy link
Collaborator

mrtheb commented Jan 16, 2014

I didn't see the other one was 60, yep, twice the other one is good. Make sure there is a comment somewhere so people know to avoid the same type of problem that triggered this change.

mrtheb added a commit that referenced this pull request Jan 17, 2014
Increase default connection timeout
@mrtheb mrtheb merged commit 6db14de into dpkp:master Jan 17, 2014
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.

2 participants