[
https://issues.apache.org/jira/browse/ARTEMIS-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15636323#comment-15636323
]
ASF subversion and git services commented on ARTEMIS-833:
---------------------------------------------------------
Commit 749b831adce7ed4e43f12ad7852bdea8b9ad8c64 in activemq-artemis's branch
refs/heads/ARTEMIS-780 from [~raggz]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=749b831 ]
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)
