[jira] [Commented] (ARTEMIS-833) maxHops defaults to 0 when creating artemis cluster configuration through cli

["Martyn Taylor (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARTEMIS-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15905067#comment-15905067 ] 

Martyn Taylor commented on ARTEMIS-833:
---------------------------------------

[~clebertsuconic] [~raggz] This should be fixed, I've ran into this issue myself and it's not obvious what the problem is.  We should have this set to 1 out of the box.

> 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.15#6346)