[jira] Resolved: (SMX4NMR-175) [clustering] Replicated messages inadvertently consumed by other multicast-enabled brokers on the network

["Eoghan Glynn (JIRA)" <ji...@apache.org>]

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

Eoghan Glynn resolved SMX4NMR-175.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 1.1.0

Fix [committed|http://svn.apache.org/viewvc?rev=888786&view=rev]

> [clustering] Replicated messages inadvertently consumed by other multicast-enabled brokers on the network   
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: SMX4NMR-175
>                 URL: https://issues.apache.org/activemq/browse/SMX4NMR-175
>             Project: ServiceMix NMR
>          Issue Type: Bug
>            Reporter: Eoghan Glynn
>            Assignee: Eoghan Glynn
>             Fix For: 1.1.0
>
>
> The same cluster destination name is used by default ("org.apache.servicemix.jbi.cluster") and multicast discovery is enabled by default on the ActiiveMQ broker started via etc/activemq-broker.xml.
> As a result, replicated messages may be eagerly consumed by other multicast-enabled brokers on the network *before* they can be dequeued by the intended cluster member.
> Changing the destinationName via etc/org.apache.servicemix.jbi.cluster.config.cfg only works if done in advance before the SMX instance is started, not dynamically via config:edit etc. as in the latter case the conduit to the original destination is already set up. This is inconvenient for testing of newly installed remote instances.
> So the work-around is to allow the destinationName be over-ridden via a new system property,  "servicemix.cluster.destination".

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