x-dead-letter-exchange in Bunny Channel using default value -retry and not configuration value set.
#25
anuonifade
started this conversation in
General
Replies: 1 comment 1 reply
|
@anuonifade channels do not control what optional queue arguments like DLX keys will be. In other words, you can use a custom channel or not, the question is what will be passed on to Setting Bunny log level to It's weird to see Another thing that immediately stands out: Bunny explicitly prohibits sharing channels between threads and it is very likely that this will happen in your code. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
When creating a Bunny channel with default options set, If I try to connect to the queue with default
x-dead-letter-exchangeset by sneaker, it throws an error.Here is my sneaker configuration for Bunny
The Queue causing error is defined below.
This is the way I am using it
If I don't add the retry_exchange option to the worker
IamProfileUpdateWorker, I get the following erroractivejob-retryis the default name set for the MaxRetry queue during config but it seems Bunny isn't using it when creating the connection.Is there something I am not doing right?
All reactions