flush connection used to be available at domain level, but this is now gone and only at managed server level [domain@localhost:9999 data-source=ExampleDS] :read-operation-names { "outcome" => "success", "result" => [ "flush-all-connection-in-pool", "flush-idle-connection-in-pool", "read-attribute", "read-children-names", "read-children-resources", "read-children-types", "read-operation-description", "read-operation-names", "read-resource", "read-resource-description", "test-connection-in-pool" ] } [domain@localhost:9999 data-source=ExampleDS] pwd /host=master/server=server-one/subsystem=datasources/data-source=ExampleDS and [domain@localhost:9999 data-source=ExampleDS] :read-operation-names { "outcome" => "success", "result" => [ "add", "disable", "enable", "read-attribute", "read-children-names", "read-children-resources", "read-children-types", "read-operation-description", "read-operation-names", "read-resource", "read-resource-description", "remove", "undefine-attribute", "whoami", "write-attribute" ] } [domain@localhost:9999 data-source=ExampleDS] pwd /profile=default/subsystem=datasources/data-source=ExampleDS Also there are now 2 commands to support: "flush-all-connection-in-pool", "flush-idle-connection-in-pool",
priority=high, blocks 707223, target release = 3.1 per BZ triage (crouch, asantos, loleary, mfoley)
Split Datasources subsystem into three subsystems based on the parent server type (Standalone, Managed, and Profile). Each new subsystem has only applicable properties, metrics and operations. This follows the same solution used for the Transactions subsystem, the only difference is the usage of entity&include to reduce the number of lines of XML.
Bulk closing of items that are on_qa and in old RHQ releases, which are out for a long time and where the issue has not been re-opened since.