Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Make consumer_timeout configurable via TLS Parameters #3344

Closed
chrisjsewell opened this issue Aug 30, 2021 · 2 comments
Closed

Make consumer_timeout configurable via TLS Parameters #3344

chrisjsewell opened this issue Aug 30, 2021 · 2 comments

Comments

@chrisjsewell
Copy link

chrisjsewell commented Aug 30, 2021

#2990, it's fair to say, is not a universally loved change; for myself, it kind of breaks our whole program 😢.

One compromise I believe makes sense, is to allow consumer_timeout to be set by the consumer, as part of the connection URI (preferably allowing for false), since it seems reasonable the client should have a say in how long it may take to complete a task.

See: https://www.rabbitmq.com/uri-query-parameters.html#tls

Originally posted in #2990 (comment)

@chrisjsewell
Copy link
Author

No experience with erlang; but happy to try a PR if what I suggest seems amenable 😬

@michaelklishin
Copy link
Member

I will convert this issue to a GitHub discussion. Currently GitHub will automatically close and lock the issue even though your question will be transferred and responded to elsewhere. This is to let you know that we do not intend to ignore this but this is how the current GitHub conversion mechanism makes it seem for the users :(

@rabbitmq rabbitmq locked and limited conversation to collaborators Aug 30, 2021

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants