[jira] [Updated] (ARTEMIS-1688) Cluster won't form when auto-create-addresses = false

["Justin Bertram (JIRA)" <ji...@apache.org>]

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

Justin Bertram updated ARTEMIS-1688:
------------------------------------
    Description: 
If address auto-creation is disabled like so:

{noformat}
<address-setting match="#">
   <auto-create-queues>false</auto-create-queues>
   <auto-create-addresses>false</auto-create-addresses>
</address-setting>
{noformat}

Then the cluster bridge will silently fail to connect because its notification consumer (see org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionBridge#setupNotificationConsumer) will fail.

To workaround this issue the management notifications address can be manually configured like so:

{noformat}
<address name="activemq.notifications">
   <multicast/>
</address>
{noformat}

> Cluster won't form when auto-create-addresses = false
> -----------------------------------------------------
>
>                 Key: ARTEMIS-1688
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1688
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 2.4.0
>            Reporter: Justin Bertram
>            Assignee: Justin Bertram
>            Priority: Major
>
> If address auto-creation is disabled like so:
> {noformat}
> <address-setting match="#">
>    <auto-create-queues>false</auto-create-queues>
>    <auto-create-addresses>false</auto-create-addresses>
> </address-setting>
> {noformat}
> Then the cluster bridge will silently fail to connect because its notification consumer (see org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionBridge#setupNotificationConsumer) will fail.
> To workaround this issue the management notifications address can be manually configured like so:
> {noformat}
> <address name="activemq.notifications">
>    <multicast/>
> </address>
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)