another fix to make amqp messages go to a separate queue #12313
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sending to a different exchange isn't enough as it will still "fan out" to the default "messages" queue
javiereguiluz
approved these changes
Sep 12, 2019
|
Thanks Ryan. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Sorry! Missed this detail from my PR yesterday. Because the default queue is always named "messages", you need to send to a separate exchange (because exchanges are "fan out" by default... so you need a different exchange per queue if you keep this setting... which is the easiest) and also configure that exchange to bind to a queue of a different name. The end result is that the 2 transports will send messages to 2 separate queues.