You know. I don’t think this is actually possible.
I think the ‘producer’ for advisories is actually the broker itself. Which
makes sense.
So you can’t track down which host consumed or produced a message.
Kevin
On Sat, Feb 14, 2015 at 10:35 AM, Kevin Burton bur...@spinn3r.com wrote:
You
On Sat, Feb 14, 2015 at 6:56 PM, Tim Bain tb...@alumni.duke.edu wrote:
Are you really looking for every message to result in a second message
going to the advisory topic, especially at the volume you've described for
your use cases? This seems like a good opportunity to rethink this part of
Are you really looking for every message to result in a second message
going to the advisory topic, especially at the volume you've described for
your use cases? This seems like a good opportunity to rethink this part of
your solution (and we'll help of you'd like).
On Feb 14, 2015 3:36 PM, Kevin
I don't believe there's an advisory for that.
Can you have the consumer fire an event back over the message bus? Either
in request/reply style (using, for example, the JMSReplyTo address), or in
event-notification style (such as with a Topic or VirtualTopic).
--
View this message in context:
You mean like “ I just consumed this message and my hostname is X
On Fri, Feb 13, 2015 at 9:48 PM, artnaseef a...@artnaseef.com wrote:
I don't believe there's an advisory for that.
Can you have the consumer fire an event back over the message bus? Either
in request/reply style (using, for
Hi Kevin,
For setting a custom ID, use the oft-overlooked ActiveMQConnection /
Connection setClientID() method. Just be sure to use a unique one per
client, ActiveMQ will reject dupes. I haven¹t used Advisories for that
before, but, setClientID is really useful for inventory.
Thanks,
Justin
