[ 
https://issues.apache.org/activemq/browse/AMQ-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dejan Bosanac updated AMQ-2359:
-------------------------------

    Description: 
When you include statically destinations with wildcards, such as

{code}<staticallyIncludedDestinations>
  <topic physicalName=">"/>
</staticallyIncludedDestinations>{code}

you will receive duplicate messages on the receive broker side. The problem is 
the reversed destination filter matching while adding an interest to the 
demandsubscription in the conduit bridge. It will not match that we already 
have a consumer for all destinations and will add another consumer for the 
particular destination.

  was:
When you include statically destinations with wildcards, such as

{code}
        <staticallyIncludedDestinations>
          <topic physicalName=">"/>
        </staticallyIncludedDestinations>
{code}

you will receive duplicate messages on the receive broker side. The problem is 
the reversed destination filter matching while adding an interest to the 
demandsubscription in the conduit bridge. It will not match that we already 
have a consumer for all destinations and will add another consumer for the 
particular destination.


> staticallyIncludedDestinations set in a Network of Brokers results in 
> duplicate messages
> ----------------------------------------------------------------------------------------
>
>                 Key: AMQ-2359
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2359
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.2.0
>            Reporter: Dejan Bosanac
>            Assignee: Dejan Bosanac
>             Fix For: 5.3.0
>
>
> When you include statically destinations with wildcards, such as
> {code}<staticallyIncludedDestinations>
>   <topic physicalName=">"/>
> </staticallyIncludedDestinations>{code}
> you will receive duplicate messages on the receive broker side. The problem 
> is the reversed destination filter matching while adding an interest to the 
> demandsubscription in the conduit bridge. It will not match that we already 
> have a consumer for all destinations and will add another consumer for the 
> particular destination.

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

Reply via email to