[
https://issues.apache.org/jira/browse/ARTEMIS-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15628246#comment-15628246
]
ASF GitHub Bot commented on ARTEMIS-833:
----------------------------------------
GitHub user TomRoss opened a pull request:
https://github.com/apache/activemq-artemis/pull/878
ARTEMIS-833 maxHops defaults to 0 when creating artemis cluster confi
through cli
https://issues.apache.org/jira/browse/ARTEMIS-833
The generated broker.xml configuration file has the <max-hops/> element
set to 0. This is very confusing since it effectively disables message
load balancing and stop cluster from forwarding messages to other nodes
in hte cluster. This should be set to at least 1.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/TomRoss/activemq-artemis artemis-833
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/878.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #878
----
commit 719ddced7b1f91e4212c20e8a7fc4b488f125842
Author: Tom Ross <[email protected]>
Date: 2016-11-02T08:47:16Z
ARTEMIS-833 maxHops defaults to 0 when creating artemis cluster
configuration through cli
https://issues.apache.org/jira/browse/ARTEMIS-833
The generated broker.xml configuration file has the <max-hops/> element
set to 0. This is very confusing since it effectively disables message
load balancing and stop cluster from forwarding messages to other nodes
in hte cluster. This should be set to at least 1.
----
> maxHops defaults to 0 when creating artemis cluster configuration through cli
> ------------------------------------------------------------------------------
>
> Key: ARTEMIS-833
> URL: https://issues.apache.org/jira/browse/ARTEMIS-833
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 1.4.0
> Reporter: Tom Ross
> Priority: Minor
> Labels: easyfix
>
> When running artemis CLI to create cluster configuration using simple CLI
> command like:
> {noformat}
> ./artemis create --clustered --name node-one --host localhost
> --message-load-balancing ON_DEMAND ../node-one
> {noformat}
> The generated broker.xml configuration file has the <max-hops/> element set
> to 0. This is very confusing since it effectively disables message load
> balancing and stop cluster from forwarding messages to other nodes in hte
> cluster. This should be set to at least 1.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)