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

Broken pipe or closed connection #30

Open
Mulkave opened this issue Oct 12, 2018 · 4 comments
Open

Broken pipe or closed connection #30

Mulkave opened this issue Oct 12, 2018 · 4 comments
Assignees
Labels

Comments

@Mulkave
Copy link
Member

Mulkave commented Oct 12, 2018

There needs to be a class that handles connections and re-connects on failure.

According to this comment, it should work fine.

@snezhkoigor
Copy link

Have some news from here?

@KinaneD
Copy link
Member

KinaneD commented Feb 18, 2019

Hello @snezhkoigor, this depends on your case. Is processing a message taking more time than the default timeout values before this exception is thrown?
In the release, the default timeouts variable are now configurable. Try modifying these according to your needs.

@snezhkoigor
Copy link

if I set connection_timeout = 0 connection to rabbit will be forever?

@KinaneD
Copy link
Member

KinaneD commented Feb 20, 2019

Not sure how it would behave, but i presume that a connection would never be established.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants