Hi Gary,
Thanks for your thoughtful response once again.
I tried adding htis call in my code:
connectionFactory.setClientIDPrefix("ID:ReplyDest.hostname");
And then added this in activemq.xml in staticallyIncludedDestinations tag:
"/>
However I noticed that ActiveMQ ignored prefix string set from
setClientIDPrefix call and still when I called
session.createTemporaryQueue() it created temp queue names as
"temp-queue://ID:host-40202-1301003416073-0:1:1"
And because of that wildcard match failed inside
staticallyIncludedDestinations.
However when create a named queue like this:
session.createQueue("ReplyDest.host-client-queue-" + new Date());
And have this ReplyDest. configured in staticallyIncludedDestinations then
request response flow through just fine, however since I'm putting Date() in
queue name (to make it unique per instance) I see lots of those queues on
AMQ console which I believe will be confusing to our operations folks. Is
there anyway AMQ can clear these queues once there is no consumer?
cheers,
Anubhava
--
View this message in context:
http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3403957.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
