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

Bug 1117785

Summary: JDBC drivers reference wrong profile
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Heiko Braun <hbraun>
Component: Web ConsoleAssignee: Heiko Braun <hbraun>
Status: CLOSED DUPLICATE QA Contact: Jakub Cechacek <jcechace>
Severity: high Docs Contact: Russell Dickenson <rdickens>
Priority: unspecified    
Version: unspecifiedCC: brian.stansberry, hpehl, jkudrnac, rhatlapa, rpulluru, smaestri
Target Milestone: ---   
Target Release: EAP 6.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-08 06:39:17 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: 900675    
Bug Blocks: 1118239    

Description Heiko Braun 2014-07-09 11:50:10 UTC
I can see a different behaviour in listing of drivers.

There are 3 servers present in host.xml file
and 2 servers are using full profile with auto-start="true"
and 1 server is using full-ha profile with auto-start="false"

Steps to reproduce:

1) Add a module through the cli
     module add --name=com.oracle.jdbc --resources=/path of/ojdbc6.jar --dependencies=javax.api,javax.transaction.api

2) Register JDBC driver:
   /profile=full/subsystem=datasources/jdbc-driver=oracle:add(driver-module-name=com.oracle.jdbc,driver-name=oracle,driver-xa-datasource-class-name=oracle.jdbc.xa.client.OracleXADataSource)

3) Restart JBoss server EAP 6.2.1 by using domain.sh

4) Login to Management Console -> select Profiles "Default" and then you can create the datasource for the oracle driver in 'default' profile succesfully.
   Which is wrong.

5) Open the domain.xml file and you can see the datasource created successfully in default profile but driver is not registered yet in default profile.


Is this a inter linked bug or Should I file other bug for this issue.

Comment 1 Heiko Braun 2014-07-09 11:56:19 UTC
@Stefano

Can you comment on this? I am not sure what the constraint is between subsystem=datasources/jdbc-driver=* and profiles and how this affects the outcome of /subsystem=datasources:installed-drivers(), which is the operation we use to provide a choice of drivers when creating a datasource.

Comment 2 Heiko Braun 2014-07-09 12:00:24 UTC
@rpulluru 

Not sure if your observation is correct:

"4) Login to Management Console -> select Profiles "Default" and then you can create the datasource for the oracle driver in 'default' profile successfully.
   Which is wrong."

The driver has been added as a module and is thus available to all profiles. But let's wait for smaestri to comment on the expected behaviour.

Comment 3 Heiko Braun 2014-07-09 12:05:01 UTC
I think this is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=900675

Comment 4 Jakub Cechacek 2014-07-16 10:54:42 UTC
Moving to 6.4 as the issue is still valid for 6.3

Comment 5 Heiko Braun 2014-10-08 06:39:17 UTC

*** This bug has been marked as a duplicate of bug 1118239 ***

Comment 6 JBoss JIRA Server 2014-10-08 06:39:36 UTC
Heiko Braun <ike.braun> updated the status of jira HAL-446 to Closed

Comment 7 Red Hat Bugzilla 2023-09-14 02:11:17 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days