For the Message class - the MessageId will be unique - and won't
change from broker to broker. In fact, the toString() method on this
class returns the same value used by the getJMSMessageID() on the
derived class ActiveMQMessage
cheers,
Rob Davies
'Go further faster with Apache Camel!'
http://rajdavies.blogspot.com/
On Jul 24, 2007, at 10:12 AM, davidmc wrote:
Hello folks,
I have a question for someone who knows the broker code well...
When a broker relays a message to another broker through a network
connector, a new message is produced which has the same content, but a
different CommandID.
Among the many IDs that you can find in the Message class, is there
any ID
or combination of IDs that can tie the outgoing message to the
incoming one?
For example, I tried with the correlationID field and found its
value is
always null, so it was not useful...
I would like to know this in order to be able to trace the 'travel
path' of
a message who goes from a producer to a consumer, but through more
than 1
broker, in a scenario with many producers, consumers, and networked
brokers.
Thanks in advance :)
David
--
View this message in context: http://www.nabble.com/Broker-
internals---tracing-a-message-questions-tf4134634s2354.html#a11759387
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
