Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1073537 - DS connection tests is required to pass across all servers
DS connection tests is required to pass across all servers
Status: CLOSED CURRENTRELEASE
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web Console (Show other bugs)
6.2.0
Unspecified Unspecified
unspecified Severity high
: DR3
: EAP 6.3.0
Assigned To: Harald Pehl
Jakub Cechacek
Russell Dickenson
:
Depends On: 1072962
Blocks:
  Show dependency treegraph
 
Reported: 2014-03-06 11:12 EST by Jakub Cechacek
Modified: 2015-02-01 18:00 EST (History)
5 users (show)

See Also:
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 11:41:24 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
JBoss Issue Tracker HAL-384 Major Resolved DS connection tests is required to pass across all servers 2014-07-24 03:29:00 EDT

  None (edit)
Description Jakub Cechacek 2014-03-06 11:12:04 EST
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")
            ]
        }
    ]
}
Comment 1 JBoss JIRA Server 2014-03-07 05:44:31 EST
Harald Pehl <hpehl@redhat.com> updated the status of jira HAL-384 to Coding In Progress
Comment 2 JBoss JIRA Server 2014-03-07 08:02:22 EST
Harald Pehl <hpehl@redhat.com> updated the status of jira HAL-384 to Resolved
Comment 3 Jakub Cechacek 2014-04-07 06:14:59 EDT
verified with 6.3.0.DR6

Note You need to log in before you can comment on or make changes to this bug.