That's where the settings for watchTopicAdvisories on the connection comes into the play. By default connection subscribers to temp topics advisories, so it knows if valid temporary destination exists on the broker (without making rpc calls by some other mechanism). If you don't use temps, it safe to set your connection url to something like
tcp://localhost:61616?jms.watchTopicAdvisories=false to disable this. Regards -- Dejan Bosanac ---------------------- Red Hat, Inc. FuseSource is now part of Red Hat dbosa...@redhat.com Twitter: @dejanb Blog: http://sensatic.net ActiveMQ in Action: http://www.manning.com/snyder/ On Wed, Feb 12, 2014 at 3:37 PM, khandelwalanuj <khandelwal.anu...@gmail.com > wrote: > I saw the page you specified but not found any information for > "topic://ActiveMQ.Advisory.TempQueue_Advisory.TempTopic". What is the > relation between temp destinations and advisories ? > > > Thanks, > Anuj > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Disable-advisory-for-ActiveMQ-broker-tp4677863p4677867.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
