[rabbitmq-discuss] Trace Plugin

Wed May 29 13:36:21 BST 2013

Apologies for bumping earlier: I didn't see the mail.

I think this is cluster related (I didn't mention the cluster earlier, sorry)

It seems that the fire-hose tracing only seems to allow tracing on the first node that is started in the cluster.
ie The consumer needs to connect to the node that was started first.
If I connect the consumer to a node that wasn't started first, messages aren't routed to the declared queue.

Is this the case ?

I am able to run trace_on and trace_off and see the messages start and stop at the consumer with no problems. (With out re-creating the channel).

Thanks

Jeff

-----Original Message-----
From: Matthias Radestock [mailto:matthias at rabbitmq.com] 
Sent: Wednesday, May 29, 2013 10:26 AM
To: Jeffery, Mark
Cc: Discussions about RabbitMQ
Subject: Re: [rabbitmq-discuss] Trace Plugin

Jeff,

On 28/05/13 13:52, Jeffery, Mark wrote:
> I have the following scenario that led to my question
>
> On 3.0.1 if I (via Java, not management console)
>
> Have the rabbitmq_tracing plugin enabled Declare a queue 
> "tracepublish"
> Bind it to exchange amq.rabbitmq.trace with routing key publish.# 
> Start a Consumer on "tracepublish"
> Execute rabbitmqctl trace_on
>
> I receive all the messages published perfectly.
>
> However if I
> Disable the rabbitmq_tracing plugin.
> Declare a queue "tracepublish"
> Bind it to exchange amq.rabbitmq.trace with routing key publish.# 
> Start a Consumer on "tracepublish"
> Execute rabbitmqctl trace_on
>
> I get no messages on the consumer side. Almost as though the firehose 
> tracing was disabled when the plugin was disabled

I can see nothing in the code that would cause that to happen. Check the logs for "{Enabling,Disabling} tracing for vhost ..." messages. Any change in the tracing should be accompanied by these.

Note that the tracing state is checked on channel creation only, so enabling/disabling tracing after a channel has been created has no effect on the tracing of messages published/consumed on that channel. I wonder whether that could explain the difference in behaviour you were seeing.

Regards,

Matthias.
To read FirstRand Bank's Disclaimer for this email click on the following address or copy into your Internet browser: 
https://www.fnb.co.za/disclaimer.html 

If you are unable to access the Disclaimer, send a blank e-mail to
firstrandbankdisclaimer at fnb.co.za and we will send you a copy of the Disclaimer.