For DS connection tests to succeed it currently has to pass across all servers instead only on those using currently selected profile. Steps to reproduce: 1) unzip distribution 2) start EAP domain 3) start other-server-group 4) navigate to web console -> datasources 5) pick full profile and DISABLE DefaultDS 6) switch to full-ha profile and test connection to DefaultDS DS actual result: Test failed expected result: Test was successful The problem is in the composite operation used to execute this test (Only the second step should be present in this case) -- see bellow. Because of this I am also concerned about the performance of this solution in large domains (10s of nodes, 100s of servers). Request { "address" => [], "operation" => "composite", "steps" => [ { "operation" => "test-connection-in-pool", "address" => [ ("host" => "master"), ("server" => "server-one"), ("subsystem" => "datasources"), ("data-source" => "ExampleDS") ] }, { "operation" => "test-connection-in-pool", "address" => [ ("host" => "master"), ("server" => "server-three"), ("subsystem" => "datasources"), ("data-source" => "ExampleDS") ] }, { "operation" => "test-connection-in-pool", "address" => [ ("host" => "master"), ("server" => "server-two"), ("subsystem" => "datasources"), ("data-source" => "ExampleDS") ] } ] }
Harald Pehl <hpehl> updated the status of jira HAL-384 to Coding In Progress
Harald Pehl <hpehl> updated the status of jira HAL-384 to Resolved
verified with 6.3.0.DR6