[
https://issues.apache.org/jira/browse/ARTEMIS-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630829#comment-15630829
]
ASF subversion and git services commented on ARTEMIS-833:
---------------------------------------------------------
Commit e89f6a1bfdc6a29422022717e231234c150f314b in activemq-artemis's branch
refs/heads/master from Clebert Suconic
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=e89f6a1 ]
Revert "ARTEMIS-833 maxHops defaults to 0 when creating artemis cluster
configuration through cli"
this is breaking client size load balance example.
This reverts commit 3de65682cecfaf2f37ae41cd709d983cd0418c3c.
> 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)
