Currently there is no support for creating Cluster connections and defining static connections (only discovery group) in admin console. However "Direct connections" attribute can be set only for clusters with defined static connections, thus it cannot be set for clusters with defined Discovery group. With no support for static connections I think the option for setting this attribute should be removed.
I claim thee.
After discussion with bbaranow I have realized that it is not a good idea to actually remove this property because there potentially could be a connection which was previously properly created or configured (including needed static connectors) via Cli. However part of this issue is "Unknown error" which is being thrown whenever you try to enable this property on connection without static connector. I believe that some more specific error, which will describe what actually happened, should be raised instead. I have also rephrased the title to reflect the issue more precisely
This is wicked, console output: Message Cancel Wed Apr 17 10:37:53 CEST 2013 Unknown error Unexpected HTTP response: 500 Request { "operation" => "composite", "address" => [], "steps" => [{ "address" => [ ("subsystem" => "messaging"), ("hornetq-server" => "default"), ("cluster-connection" => "CC") ], "operation" => "write-attribute", "name" => "allow-direct-connections-only", "value" => true, "child-type" => undefined }] } What AS shows in debug: DEBUG [org.jboss.as.controller.management-operation] (XNIO-1 task-5) JBAS014616: Operation ("write-attribute") failed - address: ([ ("subsystem" => "messaging"), ("hornetq-server" => "default"), ("cluster-connection" => "CC") ]) - failure description: "JBAS011630: Alternative attribute of (allow-direct-connections-only) is already defined."
There is no way to determine if static connectors have been defined, hence it makes little sense to have this property. Its like having a button in house, which will turn wipers in car you might not even have. Ive talked with <hpehl>. There will be separate issue, which will introduce static-connectors.
https://issues.jboss.org/browse/AS7-6939 https://github.com/hal/core/pull/4
Brian Stansberry <brian.stansberry> made a comment on jira AS7-6939 This is merged in HAL; AS7 issue can be resolved when a version of the console with the fix in it is merged.
This seems to be OK. Status will be appropriately changed once verified by console test-suite (run currently in progress).
Verified 6.1.1.ER2
Sounds like this issue was transitioned to another ticket. Switching 'requires doc text' flag to '-' to remove from Release Notes list. Please comment and reflag if I've misunderstood.