ASF GitHub Bot commented on ARTEMIS-1688:

GitHub user jbertram opened a pull request:


    ARTEMIS-1688 fix cluster when auto-create-addresses=false


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jbertram/activemq-artemis ARTEMIS-1688

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1879
commit 6fe0848760091b269e93efd4ae55c7169576ef34
Author: Justin Bertram <jbertram@...>
Date:   2018-02-20T00:46:32Z

    ARTEMIS-1688 fix cluster when auto-create-addresses=false


> 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
>             Fix For: 2.5.0
> 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

Reply via email to