You're right, Ben. This is still rather flaky. 

I've reopened the jira. 

Thanks,
Joe



Benjamin April wrote:
> 
> Joe Fernandez wrote:
>> Ben,
>>
>> I just ran a quick test with my 5.1 setup and everything worked as
>> expected.
>> With the networkConnector below, only messages destined for queues with a
>> prefix of "Q." were excluded from being forwarded and only messages
>> destined
>> for topics with a prefix of "local." were excluded. 
>>
>> <networkConnector name="test1" uri="static://(tcp://localhost:61617)">       
>>         <excludedDestinations>
>>          <queue physicalName="Q.>"/>     
>>          <topic physicalName="local.>"/>         
>>         </excludedDestinations>
>> </networkConnector> 
>>
>> Joe
>>
>>
>>   
> Joe,
> 
>     I think I found the issue. I bet it will break and not forward 
> anything if you try:
> 
>         <excludedDestinations>
>          <queue physicalName="local.>"/>     
>          <topic physicalName="local.>"/>         
>         </excludedDestinations>
> 
>   also with the sample config you provide a queue called local.foo will
> not be forwarded nor will a topic with the name Q.foo. I can live with
> this result as I want to be able to say anything starting with "local." is
> not forwarded, but I think the doc may be misleading here. 
> 
> 
> Thanks
> ben
> 
> 
> 
>> Benjamin April wrote:
>>   
>>> Joe Fernandez wrote:
>>>     
>>>> See the following JIRA
>>>>
>>>> https://issues.apache.org/activemq/browse/AMQ-1629
>>>>
>>>> Joe
>>>> Get a free ActiveMQ user guide @ http://www.ttmsolutions.com
>>>>
>>>>
>>>>
>>>>   
>>>>       
>>> That JIRA claims the fix version is 5.1.0. My issue was with 5.1.0. 
>>> Should I take that to mean
>>> that the fix was released as part of 5.1.0 or that it was added during 
>>> the life of 5.1.0 and should
>>> be found in 5.2.*?
>>>
>>> Thanks
>>> Ben
>>>
>>>     
>>>> Benjamin April wrote:
>>>>   
>>>>       
>>>>> Greetings,
>>>>>
>>>>> I have 2 ActiveMQ nodes (both 5.1.0).  They are linked via static TCP 
>>>>> networkConnector statements:
>>>>>
>>>>> [host-1]
>>>>>  <networkConnector uri="static://(tcp://10.0.0.202:61616)"
>>>>>   name="host-2"
>>>>>   dynamicOnly="true"
>>>>>   conduitSubscriptions="false"
>>>>>   decreaseNetworkConsumerPriority="false">
>>>>>  </networkConnector>
>>>>>
>>>>> [host-2]
>>>>>  <networkConnector uri="static://(tcp://10.0.0.201:61616)"
>>>>>   name="host-1"
>>>>>   dynamicOnly="true"
>>>>>   conduitSubscriptions="false"
>>>>>   decreaseNetworkConsumerPriority="false">
>>>>>  </networkConnector>
>>>>>
>>>>> Everything works fine. If Host-2 has a subscriber on topic foo and 
>>>>> someone sends a message to topic foo on host-1 the subscriber gets a
>>>>> copy.
>>>>> When I add the following config things break down.
>>>>>
>>>>>   <excludedDestinations>
>>>>>    <queue physicalName="local.>"/>
>>>>>    <topic physicalName="local.>"/>
>>>>>   </excludedDestinations>
>>>>>
>>>>> With no wildcards things work as I would expect. The listed topics or 
>>>>> queues are not propagated and topics not listed in the exclude
>>>>> directive 
>>>>> are propagated. However with wildcards NO topics or queue are 
>>>>> propagated. I also tried "local.*". According to 
>>>>> http://activemq.apache.org/networks-of-brokers.html this should work.
>>>>>
>>>>> Just for reference (I may have this part wrong) the entire 
>>>>> networkConnector block appears as follows with the exclude:
>>>>>
>>>>>  <networkConnector uri="static://(tcp://10.0.0.201:61616)"
>>>>>   name="host-1"
>>>>>   dynamicOnly="true"
>>>>>   conduitSubscriptions="false"
>>>>>   decreaseNetworkConsumerPriority="false">
>>>>>   <excludedDestinations>
>>>>>    <queue physicalName="local.>"/>
>>>>>    <topic physicalName="local.>"/>
>>>>>   </excludedDestinations>
>>>>>  </networkConnector>
>>>>>
>>>>> Can anyone point me in the right direction here?
>>>>>
>>>>> Thanks for any help
>>>>>
>>>>> Ben
>>>>>
>>>>>
>>>>> TREND MICRO EMAIL NOTICE
>>>>> The information contained in this email and any attachments is
>>>>> confidential and may be subject to copyright or other intellectual
>>>>> property protection. If you are not the intended recipient, you are
>>>>> not
>>>>> authorized to use or disclose this information, and we request that
>>>>> you
>>>>> notify us by reply mail or telephone and delete the original message
>>>>> from
>>>>> your mail system.
>>>>>
>>>>>
>>>>>     
>>>>>         
>>>>   
>>>>       
>>>
>>>     
>>
>>   
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Problem-with-excludedDestinations-tp19958538p19972528.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Reply via email to