Hi,
You'll need to adjust your broker url. Adding advisorySupport="false" is
not enough to completely disable advisory messages. You'll need to change
the broker url in your ConnectionFactory to: tcp://localhost:61616
?jms.watchTopicAdvisories=false
Regards,
Richard
http://richardlog.com
On Sat
Hi.
Sorry. i need help please
I am using ActiveMQ and Spring JMS template.
follow your steps, but do not work my setting.
show it my conf.
advisorySupport="false">
No. You have to disable advisory support, and the
jms.watchTopicAdvisories=false needs to go on the client (or you can
setWatchTopicAdvisories(false) on the connectionFactory). You may also
want to disable creation of advisory topics via ActiveMQ authorization
security to enforce this policy (alth
Hi,
I tried setting connection URI in broker config as:
*
*
but still it is creating advisories for tmp topics. But when I changed
configuration on client side and make "watchTopicAdvisories=false" in client
consiguration, I can avoid tmp advisories.
Is there a way to di
Okay.. So I need to do :* advisorySupport="false" * as well as
*tcp://localhost:61616?jms.watchTopicAdvisories=false*
to get rid of advisories completely.
Just one thing that if i use above configuration, is there any side effect/
impact on other things of broker ?
(I am basically doing it to im
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
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-Act
Hi Anuj,
you can find more info here
http://activemq.apache.org/advisory-message.html#AdvisoryMessage-Disablingadvisorymessages
the only side effect is that dynamic broker networks will not work. You
should set connection property for that last advisory to not be used.
Regards
--
Dejan Bosanac
