That depends what you mean by "trace". If you mean "get counts per
destination at a point in time, so you can subtract the values at two times
to find the number of messages in that time period", you can use the web
console or JMX to get that information. If you mean something else, please
explai
Is there a way to trace all messages passing through a broker?
In that way I could verify what load the server is under.
>Statically including all destinations will send messages for all
>destinations to the central broker when all consumers are offline, even if
>the consumers will only ever be
Do you have any evidence that advisory messages about hundreds of empty
queues actually has a measurable impact on either your central broker or
your edge brokers? It's definitely possible that the overhead of advisory
messages really is too high, but if you haven't measured it somehow and
you're
Hi Tim,
thank you for your replay and your very thoughtful questions.
>But are you sure you need to? Are you sure this isn't a premature [...]
I think so. The central broker is on our server farm and it is very
resourceful machine; anyway it often uses a lot of cpu. The broker uses
thousands of
If you know in advance which destinations are local-only and which ones
might need to be routed across the network of brokers, it's possible to
dynamically include or exclude destinations whose names match certain
patterns. See activemq.apache.org/networks-of-brokers.html for more
details.
You ca
