Thank you @gtully for your reply.
Artemis seems to make life easier. Unfortunately, I cannot switch to Artemis
at the moment.
Thus, I switched my implementation to fetch these information using JMS API
and that works pretty well (tested via a normal Java application) , but then
again came up the
that maxBrowsePageSize limit is exposed as a destination policyEntry,
you can raise it very high and then a browse will be limited by the
memory usage limits.
the point of the limit is that the messages are dispatched from
memory, there is no browser implementations that will query the
message stor
I have a custom error queue in ActiveMQ, which is populated by Apache Camel's
onException(..) error handler. There can be thousands of messages in this
queue.
Instead of using the ActiveMQ web console, I am building a custom web admin
to integrate several other statistics from other components as
