Bug 1073537
| Summary: | DS connection tests is required to pass across all servers | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Jakub Cechacek <jcechace> |
| Component: | Web Console | Assignee: | Harald Pehl <hpehl> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Jakub Cechacek <jcechace> |
| Severity: | high | Docs Contact: | Russell Dickenson <rdickens> |
| Priority: | unspecified | ||
| Version: | 6.2.0 | CC: | brian.stansberry, hbraun, jkudrnac, kkhan, smumford |
| Target Milestone: | DR3 | ||
| Target Release: | EAP 6.3.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
In previous versions of JBoss EAP 6, the DS connection test used all servers in the domain. This could negatively impact performance.
In this release of the product, only the servers of the currently selected profiles are used for the connection test, resulting in better, more reliable performance.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-06-28 15:41:24 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1072962 | ||
| Bug Blocks: | |||
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 |
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") ] } ] }