You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In lib/exchange.js, the sendMessage() method checks for opts.reply to interact with a replyQueue. However, when the exchange is created, the replyQueue is always created regardless of the value of opts.reply. This creates a bunch of un-named queues that we're not actually using (especially since a lot of our connections to an exchange are for listening to the queue instead of writing to it).
Could you check the opts and create the queue if necessary?
If that's an acceptable solution, I'd be willing to submit a PR for that check.
The text was updated successfully, but these errors were encountered:
In lib/exchange.js, the sendMessage() method checks for opts.reply to interact with a replyQueue. However, when the exchange is created, the replyQueue is always created regardless of the value of opts.reply. This creates a bunch of un-named queues that we're not actually using (especially since a lot of our connections to an exchange are for listening to the queue instead of writing to it).
Could you check the opts and create the queue if necessary?
If that's an acceptable solution, I'd be willing to submit a PR for that check.
The text was updated successfully, but these errors were encountered: