[jboss-jira] [JBoss JIRA] (WFLY-8828) Creating cluster-connection in CLI must require discovery-group or static-connector

[ https://issues.jboss.org/browse/WFLY-8828?page=com.atlassian.jira.plugin.... ] Miroslav Novak updated WFLY-8828: --------------------------------- Description: cluster-connection must require discovery-group or static-connector (exclusively, not both can be defined) but currently it's possible to create it without it: {code} [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/cluster-connection=my-cluster1:add(connector-name=connector, cluster-connection-address=jms) { "outcome" => "success", "response-headers" => { "operation-requires-reload" => true, "process-state" => "reload-required" } } [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/cluster-connection=my-cluster1:read-resource { "outcome" => "success", "result" => { "allow-direct-connections-only" => false, "call-failover-timeout" => -1L, "call-timeout" => 30000L, "check-period" => 30000L, "cluster-connection-address" => "jms", "confirmation-window-size" => 1048576, "connection-ttl" => 60000L, "connector-name" => "connector", "discovery-group" => undefined, "initial-connect-attempts" => -1, "max-hops" => 1, "max-retry-interval" => 2000L, "message-load-balancing-type" => "ON_DEMAND", "min-large-message-size" => 102400, "notification-attempts" => 2, "notification-interval" => 1000L, "producer-window-size" => -1, "reconnect-attempts" => -1, "retry-interval" => 500L, "retry-interval-multiplier" => 1.0, "static-connectors" => undefined, "use-duplicate-detection" => true }, "response-headers" => {"process-state" => "reload-required"} } {code} Such cluster-connection will not work and is hard to see where is the problem. All credit for finding this issue goes to [~wwang2016], thanks. was: cluster-connection must require discovery-group or static-connector (exclusively, not both can be defined) but currently it's possible to create it without it: {code} [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/cluster-connection=my-cluster1:add(connector-name=connector, cluster-connection-address=jms) { "outcome" => "success", "response-headers" => { "operation-requires-reload" => true, "process-state" => "reload-required" } } [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/cluster-connection=my-cluster1:read-resource { "outcome" => "success", "result" => { "allow-direct-connections-only" => false, "call-failover-timeout" => -1L, "call-timeout" => 30000L, "check-period" => 30000L, "cluster-connection-address" => "jms", "confirmation-window-size" => 1048576, "connection-ttl" => 60000L, "connector-name" => "connector", "discovery-group" => undefined, "initial-connect-attempts" => -1, "max-hops" => 1, "max-retry-interval" => 2000L, "message-load-balancing-type" => "ON_DEMAND", "min-large-message-size" => 102400, "notification-attempts" => 2, "notification-interval" => 1000L, "producer-window-size" => -1, "reconnect-attempts" => -1, "retry-interval" => 500L, "retry-interval-multiplier" => 1.0, "static-connectors" => undefined, "use-duplicate-detection" => true }, "response-headers" => {"process-state" => "reload-required"} } {code} Such cluster-connection will not work and is hard to see where is the problem. All credit for finding this issue [~wwang2016], thanks. -- This message was sent by Atlassian JIRA (v7.2.3#72005)