You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2012/07/27 15:28:41 UTC
[jira] [Closed] (AMQ-3937) watchTopicAdvisories=false doesn't work
when a consumer is subscribing to a composite topic
[ https://issues.apache.org/jira/browse/AMQ-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish closed AMQ-3937.
-----------------------------
Resolution: Not A Problem
Doesn't seem to be an issue here. If you can produce a test case that shows a problem please reopen.
> watchTopicAdvisories=false doesn't work when a consumer is subscribing to a composite topic
> -------------------------------------------------------------------------------------------
>
> Key: AMQ-3937
> URL: https://issues.apache.org/jira/browse/AMQ-3937
> Project: ActiveMQ
> Issue Type: Bug
> Reporter: Martin Chan Shu Ching
>
> When watchTopicAdvisories=false is set in ActiveMQConnectionFactory, all connection created from it will NOT listen to any advisory topics. However, when the connection is for subscribing to a composite topic, the associated advisory topic will still be listened!
> e.g.
> 1. consumer listens to TopicA,TopicB
> 2. advisory topic ActiveMQ.Advisory.Consumer.Topic.TopicA,TopicB will be created in AdvisoryBroker.addConsumer()
> 3. then AbstractRegion.addConsumer() will call DestinationMap.get(), in where when the key is TopicB, answer with value 'ActiveMQ.Advisory.Consumer.Topic.TopicA,TopicB' will return.
> Therefore, the consumer will listen to "ActiveMQ.Advisory.Consumer.Topic.TopicA,TopicB", "TopicA" and "TopicB". As such the connection still listens to an advisory topic!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira