Thank you, I was able to bridge all destinations via queue
physicalName=/ to confirm this will bridge temp destinations. Because
temp destinations use the brokerID in their name, is there a common
convention to specify only temp destinations via
dynamicallyIncludedDestinations /?
--
View this
I'm not aware of one, though I've never actually used temp destinations so
someone else might know of something I don't know about.
If there's not, you might want to submit a JIRA requesting that
ActiveMQDestination.TEMP_DESTINATION_NAME_PREFIX be made modifiable so you
can prefix all temp
Hi All,
I would like to understand the meaning of the values shown in web
console (Subscribers page) for:
* Dispatched Counter
* Enqueue Counter
* Dequeue Counter
I thought they meant the following:
* Dispatched Counter - # of messages attempted to be delivered to the
destination
* Enqueue
Thank you for your input so far, it has been helpful. Although I was able to
verify including all destinations (via wildcard) does indeed bridge
temporary destinations, I do not believe this is the intended solution for
the following reasons:
1) temp destinations are created dynamically and use
On 14-12-08 08:57 PM, Tim Bain wrote:
The log line tells you how you're doing against two different limits: the
per-destination limit and the entire-broker limit. The per-destination
limit is first, and the log line says you're using 0% of what you've
allocated per destination, so you're right
