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

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Won't Fix
• Affects Version/s: 1.4.0
• Component/s: Broker
• Labels: easyfix
• Assignee: Unassigned
• Reporter: Tom Ross
• Created: 02/Nov/16 08:31
• Updated: 22/Jan/18 21:19
• Resolved: 22/Jan/18 21:19

Description

When running artemis CLI to create cluster configuration using simple CLI command like:

./artemis create --clustered --name node-one --host localhost --message-load-balancing ON_DEMAND ../node-one

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.

Issue Links

• links to: GitHub Pull Request #878