[jboss-jira] [JBoss JIRA] (WFLY-7447) Description of cluster-name attribute in replicated ha policy does not explain behavior of undefined value

Description of cluster-name attribute in replicated ha policy does not explain behavior of undefined value ---------------------------------------------------------------------------------------------------------- Key: WFLY-7447 URL: https://issues.jboss.org/browse/WFLY-7447 Project: WildFly Issue Type: Bug Components: JMS Affects Versions: 10.1.0.Final Reporter: Jeff Mesnil Assignee: Jeff Mesnil Priority: Minor The model enables to execute following command. {code} /subsystem=messaging-activemq/server=default/ha-policy=replication-master:add {code} It creates ha policy with following configuration. {code} /subsystem=messaging-activemq/server=default/ha-policy=replication-master:read-resource { "outcome" => "success", "result" => { "check-for-live-server" => false, "cluster-name" => undefined, "group-name" => undefined, "initial-replication-sync-timeout" => 30000L }, "response-headers" => {"process-state" => "reload-required"} {code} From the description of {{cluster-name}} attribute it is not clear what is the behavior if this attribute is undefined. {code} "cluster-name" => { "type" => STRING, "description" => "Name of the cluster used for replication.", "expressions-allowed" => true, "nillable" => true, "min-length" => 1L, "max-length" => 2147483647L, "access-type" => "read-write", "storage" => "configuration", "restart-required" => "all-services" }, {code} The ActiveMQ Artemis documentation describes the attribute as follows: bq. Name of the cluster configuration to use for replication. This setting is only necessary if you configure multiple cluster connections. If configured then the connector configuration of the cluster configuration with this name will be used when connecting to the cluster to discover if a live server is already running, see `check-for-live-server`. If unset then the default cluster connections configuration is used (the first one configured).