activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Bertram (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (ARTEMIS-833) maxHops defaults to 0 when creating artemis cluster configuration through cli
Date Mon, 22 Jan 2018 21:20:00 GMT

     [ https://issues.apache.org/jira/browse/ARTEMIS-833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Justin Bertram resolved ARTEMIS-833.
------------------------------------
    Resolution: Won't Fix

> 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
(v7.6.3#76005)

Mime
View raw message