Re: [mcollective-users] Some discrepancy in direct addressing mode with reply-to

[R.I. Pienaar]

> On 28 Jan 2018, at 06:06, kk21987  wrote:
> 
> My apologize. I misunderstood few things. 
> 
> Basically when I run mco query in direct addressing mode then it publish that 
> message as queue where as broadcast mode publish the message as topic. So I 
> suspect its not an issue with the modes whatever the mco query use. The only 
> thing I want to understand is, lets say I run mco query against 1000servers 
> with --reply-to (fire and forget, no acknowledgement and nothing. Correct me 
> if am wrong), so all the response message will go to the consumer where the 
> active subscriber is present for the given queue. The response message is not 
> coming to Broker-A which I have configured by starting receiver here as well 
> and perfectly its going to the consumer where its active.

That sounds about right. Yes it will use a topic and all nodes will get it

> 
> My concern is, at the same time I see count is showing in pending message for 
> the queue "mcollective.nodes" and slowly its decreasing(at the same enqueued 
> and dequeued messages count also increasing slowly) which I have verified on 
> ActiveMQ UI Jolokia monitoring (8161). So I would like to understand why such 
> messages count in pending messages, since all I want to just fire the command 
> and forget and don't want to worry about response or whether its executed or 
> not. 
> 
> Name ↑Number Of Pending Messages  Number Of Consumers 
> Messages Enqueued   Messages Dequeued   Views   Operations
> mcollective.nodes 9   84  884 875 Browse Active Consumers
> Active Producers
>   Send To PurgeDelete
> 
> 


You will need to double check in the logs. Your client also logs and at debug 
 level you can verify where the publish to


>> On Sunday, January 28, 2018 at 7:48:15 AM UTC+5:30, kk21987 wrote:
>> 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 

Re: [mcollective-users] Some discrepancy in direct addressing mode with reply-to

[kk21987]

My apologize. I misunderstood few things. 

Basically when I run mco query in direct addressing mode then it publish 
that message as queue where as broadcast mode publish the message as topic. 
So I suspect its not an issue with the modes whatever the mco query use. 
The only thing I want to understand is, lets say I run mco query against 
1000servers with --reply-to (fire and forget, no acknowledgement and 
nothing. Correct me if am wrong), so all the response message will go to 
the consumer where the active subscriber is present for the given queue. 
The response message is not coming to Broker-A which I have configured by 
starting receiver here as well and perfectly its going to the consumer 
where its active. 

My concern is, at the same time I see count is showing in pending message 
for the queue "mcollective.nodes" and slowly its decreasing(at the same 
enqueued and dequeued messages count also increasing slowly) which I have 
verified on ActiveMQ UI Jolokia monitoring (8161). So I would like to 
understand why such messages count in pending messages, since all I want to 
just fire the command and forget and don't want to worry about response or 
whether its executed or not. 

Name ↑Number Of Pending Messages  Number Of Consumers  Messages Enqueued  
Messages 
Dequeued  Views  Operations  
mcollective.nodes 9 84 884 875 Browse Active Consumers
Active Producers
  Send To PurgeDelete

On Sunday, January 28, 2018 at 7:48:15 AM UTC+5:30, kk21987 wrote:

> 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 mcollective-users+unsubscr...@googlegroups.com.
For more options, visit 

Re: [mcollective-users] Some discrepancy in direct addressing mode with reply-to

[R.I.Pienaar]

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 mcollective-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[mcollective-users] Some discrepancy in direct addressing mode with reply-to

[kk21987]

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 
https://www.draw.io/?lightbox=1=ff=_blank=1=1=Untitled%20Diagram.xml#R3ZpNc5swEIZ%2FDcdmkMTnMXbS9tKZdHJoeqSg2Eyw5RFybPfXVwQJLAkS6vCV5JCBBS3ieXellbCFlpvjNxrt1j9IgjML2snRQjcWhH7g8f%2BF4VQaHOCXhhVNk9IEasN9%2BhcLoy2s%2BzTBuXIjIyRj6U41xmS7xTFTbBGl5KDe9kgy9am7aIUNw30cZab1V5qwdWkNoF%2Fbv%2BN0tZZPBl5YXvkTxU8rSvZb8TwLoseXv%2FLyJpK%2BxIvm6yghhzMTurXQkhLCyqPNcYmzAq3EVrb72nK16jfFW9algSNaPEfZHssuv3SMnSSMwzpl%2BH4XxcX5gettocWabTJ%2BBvhhlO9KCR7TI%2BZuF8IjpgwfW7sFqpflMYTJBjN64reIBk4g%2BIj4ATKgDrUaAAk11udKSGMkImBV%2Ba4p8AMBogWK%2FUGgmExk1xUm0vgeJhDNkgkMkcKkGkHOodhuAxRpfBcUOE8oQaBAcRuYgKZAAX0EioFkQckTptx2bcDhTfmQzk8Wb2DqgUqVBjJ9fBOL10DF7QGKmTybmBTzV5YWvZ8SSwcq7kBUwCuxcjMpFBiqGQSR24lKHyMt8Nqp3E5KBTnTUQnaoSwmDhV1Bgq65U8vkWIWbxWU5cSRMhkU6BhQTBTb5LpYJfCzOIvyPI35a%2Bcsosw0n4HhL09PD%2Fzki31l8%2BpLWH5zi33l1YY7TFPeb64Dv1AYjyl7kD74cdnArVDjxFiNaKB578mexliZYnl%2FV5idVyKmHh1HcYqziKXPai%2BaVBBPuCNpMW1VOQD0ylQrrsrei1bnyxHdkac5Qpqj8p0NRy9BUb12tzhxh4uTBr3B%2B9SeSlkQqoLAwL9QWd2RZw%2BmrDmB9qVsVwWnkkuDDMIL8xC4bzjqUS3fUKusjXNMn4upbMraWOPpImMaa1pw9zKNmQXPbLC4SMXimBsRg2EJZ4zF14Y4x9y0GoqLVGSWXLRwCcYLF2RWyPPBooeLPd7oguB8ueiDbjgilrZ9mhlg0bMIhCOmkbmmmi0X6IwYL%2BYaYjZc9DQadXgxK%2FDZcNGH3RGLF%2FSBSt1R02jOta4%2FWfHimJO0ieJzrmMdW5vs9K91XReyxjdT3VF%2FC1mnwxfSTyoX0j%2BXeKgfuQxHPcpl1jQ%2F95gfQntJtvl%2BM%2FHAA%2BQGpY7iTNKwQVJ9X%2B2ikWfAvVG5h26r2%2BeBj97aPrevXD9QttBtV5zqTbomjLrTKkNiThvrWhA4FyYW9FRHIBwusYbbfm0LHv%2F%2FvqUo%2BqJZ6avL0llf33vd0cX68tP652jl7fVP%2FtDtPw%3D%3D
 


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? 



-- 

--- 
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 mcollective-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.