Based on my understanding when I run mco query with reply-to I should see the reply-to queue name on the response header and its there on mcollective server logs, which I have verified by enabling debug on the mcollective servers.
My worry is, I shouldn't get any response messages back to the Broker-A and all the response messages should go to the consumer server which is running elsewhere. This is working as expected for broadcast based mco query but when I run direct addressing based mco query then the response message is flowing everywhere instead of going to consumer server only. I have configured the exclude destination on Broker-A to make sure none of the brokers are connected with the reply-to queue name except the consumer server broker. On Sunday, January 28, 2018 at 2:08:06 AM UTC+5:30, R.I.Pienaar wrote: > > > On Sat, 27 Jan 2018, at 15:03, kk21987 wrote: > > Hi, > > > > Am having some issue with --reply-to behavior and not sure if its an > > issue > > or the behavior itself like that. My setup is drawn in > > ...... > > > > > > My environment is enabled with direct_addressing. Basically I always > fire > > the mco and forget it and don't want to consume any messages on mco > client. > > I have configured separate consumer server where it will consume the > > messages on the queue whatever declared during the mco query and will > get > > result from thie consumer server. The reason for configured separate > > consumer server is some commands whatever I run will take more time to > > execute and also doing some logic on the response messages based on my > > requirement. > > > > I have configured exclude destination to make sure the queue whatever am > > using in reply-to not connected with Broker-A from other brokers. > > > > When I run mco query using regex filter it pubish message in broadcast > mode > > and consumer server consume the response without any issue. At the same > > time when I check on the Broker-A ActiveMQ UI monitoring I noticed > Messages > > Enqueued Dequeued count is NOT increased which means nothing coming back > to > > Broker-A. > > > > But when I run mco query using direct addressing mode (-I) along with > > reply-to the message is published as direct addressing and consumer > server > > consume the response fine here as well. At the same time when I check on > > the Broker-A ActiveMQ UI monitoring I noticed Messages Enqueued Dequeued > > count is increased which means message is coming to Broker-A as well at > the > > same time message is available on consumer server. > > > > Am not sure such difference between direct addressing and broadcast even > > though both use the same reply-to mechanism. I don't want any response > > messages come back to Broker-A and all the response messages should go > to > > Consumer Server only. Can I have some lights on this please? > > what you describe should work, I guess the best hints lie in the server > debug log. Does it send a reply and does it do so to the right target? > > > -- > R.I.Pienaar / www.devco.net / @ripienaar > -- --- You received this message because you are subscribed to the Google Groups "mcollective-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
