search

mxriverlynn / rabbus

A micro-service bus with built-in messaging patterns, for NodeJS and RabbitMQ
116 stars 26 forks source link

Request / Response created two `reply_to` queues #1

Closed rtorino closed 9 years ago

rtorino commented 9 years ago

Hi Derick,

I tried request / request (RPC) object pair and noticed that the requester creates a temporary reply_to queue and when I started the responder, it also creates another temporary queue, but only the first was used. Can you explain why?

screen shot 2014-12-25 at 15 21 49

mxriverlynn commented 9 years ago

d'oh! i had not noticed that before... but in checking my request response demo in the demo folder of the repo, it is doing that. i'll have to dig in and see if i can figure this out.

mxriverlynn commented 9 years ago

it looks like this may be a problem in Wascally... i think it is creating a response queue for every connection i make, even if i don't create or bind a queue in that connection. i'll open an issue with them and see if we can get that corrected

rtorino commented 9 years ago

I agree that this could be a problem with Wascally. Thanks!

mxriverlynn commented 9 years ago

this is by design in wascally - see referenced wascally ticket. they may change this ability in the future. but for now i'm going to close this.

infiniteluke commented 9 years ago

By adding 

{
  'replyQueue': false
}

to your config passed into wascally.configure(), you should be able to stop theses from being created. https://github.com/arobson/wascally/commit/490e6801a8726ea59015a55655404ba92d12d424

I can confirm this works on the Sender object. No more extraneous reply-to queues!