Hi,
Using ActiveMQ 5.10.
We are getting below warning messages after durable subscription gets
destroyed because it's "offlineDurableSubscriberTimeout" expired.
*From the logs: *
20141215 23:28:42.279 EST (ActiveMQ Durable Subscribe
For 1) there is a unit test that shows how to achieve a bridge with no
advisories - so statically configured - that can allow temp dests using a
naming prefix and uses destination gc to tidy up.
https://github.com/apache/activemq/blob/d54e0d6ab590b6a6148a5e2629c45b95d3f40eb8/activemq-unit-tests/src