Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 900843 (JBPAPP6-1395)

Summary: Inconsistent behavior with management console while creating a datasource
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Bharti Kundal <bkundal>
Component: Web ConsoleAssignee: Heiko Braun <ike.braun>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6.0.0CC: bkundal, brian.stansberry, hpehl, ike.braun
Target Milestone: ---   
Target Release: TBD EAP 6   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/JBPAPP6-1395
Whiteboard: eap6
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
JBoss EAP 6
Last Closed: 2013-10-02 12:52:35 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:
Attachments:
Description Flags
domain.xml
none
datasource.png none

Description Bharti Kundal 2012-09-04 09:51:41 UTC
Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A000000Au3OP&sfdc.override=1
Steps to Reproduce: 1)We can consider two profiles say a default and a full-ha(I have used these 2 for my test,behaviour does exist with all)
2)In profile "default" I created a driver as a module:
3)Created a group-group 1 for this profile and a server as serverdefault
4)When I create a datasource I can only see the drivers installed in this profile.
5)I created a server group called group2 inside full ha-profile and a server as server1 and started this server
6)Now when I try to create a datasource for profile "default",I can see the drivers which are not even installed for this profile,that is I can only see the groups from full-ha profile.
7)But when I stop these servers from group2 that is from full-ha profile, I can see the proper results that is from profile-default:group1

Now in order to check what drivers are installed for which server I use the CLI commands in order to verify whether my CLi gives me proper details
/host=master/server=server-one/subsystem=datasources:installed-drivers-list

I got the correct results:

1)For my serverdefault which belongs to group1 from profile-"default":
[domain@localhost:9999 /] /host=master/server=serverdefault/subsystem=datasources:installed-drivers-list
{
    "outcome" => "success",
    "result" => [
        {
            "driver-name" => "h2",
            "deployment-name" => undefined,
            "driver-module-name" => "com.h2database.h2",
            "module-slot" => "main",
            "driver-datasource-class-name" => "",
            "driver-xa-datasource-class-name" => "org.h2.jdbcx.JdbcDataSource",
            "driver-class-name" => "org.h2.Driver",
            "driver-major-version" => 1,
            "driver-minor-version" => 3,
            "jdbc-compliant" => true
        },
        {
            "driver-name" => "MySqlJDBCDriver",
            "deployment-name" => undefined,
            "driver-module-name" => "MySql.jdbc",
            "module-slot" => "main",
            "driver-datasource-class-name" => "",
            "driver-xa-datasource-class-name" => "",
            "driver-class-name" => "com.mysql.jdbc.Driver",
            "driver-major-version" => 5,
            "driver-minor-version" => 1,
            "jdbc-compliant" => false
        }
    ]
}

2)For my server server1 which belongs to group2 from profile:full-ha

[domain@localhost:9999 /] /host=master/server=server1/subsystem=datasources:installed-drivers-list      
{
    "outcome" => "success",
    "result" => [{
        "driver-name" => "h2",
        "deployment-name" => undefined,
        "driver-module-name" => "com.h2database.h2",
        "module-slot" => "main",
        "driver-datasource-class-name" => "",
        "driver-xa-datasource-class-name" => "org.h2.jdbcx.JdbcDataSource",
        "driver-class-name" => "org.h2.Driver",
        "driver-major-version" => 1,
        "driver-minor-version" => 3,
        "jdbc-compliant" => true
    }]
}


project_key: JBPAPP6

Inconsistent behavior is observed while we create the datasource from EAP 6 management console.

Comment 1 Bharti Kundal 2012-09-04 09:58:58 UTC
Added domain.xml and screenshots from console

Comment 2 Bharti Kundal 2012-09-04 09:58:58 UTC
Attachment: Added: domain.xml
Attachment: Added: datasource.png


Comment 3 Heiko Braun 2012-10-16 13:48:09 UTC
I don't fully understand the problem. Can you elaborate please?

Comment 4 Anne-Louise Tangring 2012-11-13 20:57:53 UTC
Docs QE Status: Removed: NEW 


Comment 6 Harald Pehl 2013-10-02 12:52:35 UTC
Cannot reproduce in current release 2.0.2.Final