activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sridhar Komandur (JIRA)" <>
Subject [jira] Created: (AMQ-1629) wildcards don't work in networkconnector excludeDestinations
Date Thu, 20 Mar 2008 14:57:32 GMT
wildcards don't work in networkconnector excludeDestinations 

                 Key: AMQ-1629
             Project: ActiveMQ
          Issue Type: Bug
          Components: Broker
    Affects Versions: 5.0.0, 4.1.1
         Environment: linux
            Reporter: Sridhar Komandur

Version: 5.0 

We have a simple setup to test excludedDestinations config ...We are using the broker and
 example producer & consumer from the binary distribution (broker instances A & B
are on different hosts 


producer --- A ---- B--- consumer 

Broker A's activemq.xml has the following for NC config (everythingelse is the same as in
the orig config file):

      <networkConnector name="toB" uri="static://(tcp://"> 
                <queue physicalName="TEST.>" /> 

Issue: consumer attached to Broker B sees all the messages sent to TEST.FOO (the default messages
generated by the producer)

We noticed that none of the queue or topic wildcards work, only specific topic or queue names
work in the exclusion. However, states
"N.B. You can use wildcards in inclusive , exclusive destination properties". Are we missing
anything ? 

- Sridhar

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message