You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Martin Chan Shu Ching (JIRA)" <ji...@apache.org> on 2012/07/18 12:15:34 UTC

[jira] [Created] (AMQ-3937) watchTopicAdvisories=false doesn't work when a consumer is subscribing to a composite topic

Martin Chan Shu Ching created AMQ-3937:
------------------------------------------

             Summary: 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

        

[jira] [Commented] (AMQ-3937) watchTopicAdvisories=false doesn't work when a consumer is subscribing to a composite topic

Posted by "Martin Chan Shu Ching (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AMQ-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418100#comment-13418100 ] 

Martin Chan Shu Ching commented on AMQ-3937:
--------------------------------------------

True. But that will disable the advisories for the whole broker. In fact, what i want is to have only a single dedicated application that listens to the advisories for analysis.
                
> 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

        

[jira] [Commented] (AMQ-3937) watchTopicAdvisories=false doesn't work when a consumer is subscribing to a composite topic

Posted by "Gary Tully (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AMQ-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13417092#comment-13417092 ] 

Gary Tully commented on AMQ-3937:
---------------------------------

watchTopicAdvisories=false is just for specific temp destination advisories so that a connection can know about temp dests without a round trip to the broker.

If you want to disable advisories, use the broker attribute advisorySupport=false

                
> 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

        

[jira] [Closed] (AMQ-3937) watchTopicAdvisories=false doesn't work when a consumer is subscribing to a composite topic

Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
     [ 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

        

[jira] [Commented] (AMQ-3937) watchTopicAdvisories=false doesn't work when a consumer is subscribing to a composite topic

Posted by "Gary Tully (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AMQ-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418191#comment-13418191 ] 

Gary Tully commented on AMQ-3937:
---------------------------------

An ActiveMQConnection *only* listens to the temp advisory topic and only when watchTopicAdvisories=true

The Advisory Topics are created on demand when the AdvisoryBroker sends messages to those topics, but there needs to be explicit consumers.

You can disable most advisories via destination policy

Note all of the boolean advisory* attributes in 
http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/broker/region/policy/PolicyEntry.java?view=markup

I am not sure there is any bug here?
                
> 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