Bug 1213642

Summary: [GSS](6.4.z) JDBC driver module-slot is not persisted in domain mode
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Lin Gao <lgao>
Component: Domain Management, JCAAssignee: Lin Gao <lgao>
Status: CLOSED CURRENTRELEASE QA Contact: Martin Simka <msimka>
Severity: unspecified Docs Contact:
Priority: high    
Version: 6.4.0CC: bmaxwell, cdewolf, dandread, harshada, istudens, jawilson, jmartisk
Target Milestone: CR1Keywords: Reopened
Target Release: EAP 6.4.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-17 10:43:50 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 1231259    

Description Lin Gao 2015-04-21 01:04:49 UTC
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:

Suppose you have a jdbc driver module: 'oracle.jdbc' with slot: '11.1'

Steps to Reproduce:
1. Start EAP 6.4 in domain mode: bin/domain.sh
2. Start EAP 6 CLI console: bin/jboss-cli.sh -c
3. Run:

/profile=full/subsystem=datasources/jdbc-driver=oracle11.1:add(driver-name=oracle11.1,driver-module-name=oracle.jdbc,driver-xa-datasource-class-name=oracle.jdbc.xa.client.OracleXADataSource,module-slot=11.1)

Actual results:
 <driver name="oracle11.1" module="oracle.jdbc">
      <xa-datasource-class>
         oracle.jdbc.xa.client.OracleXADataSource
      </xa-datasource-class>
 </driver>

 is persisted in domain.xml

Expected results:
 <driver name="oracle11.1" module="oracle.jdbc:11.1">
      <xa-datasource-class>
         oracle.jdbc.xa.client.OracleXADataSource
      </xa-datasource-class>
 </driver>

 is persisted in domain.xml

Additional info:

  The inconsistent persistence will lead to wrong module:slot used after server restarted.

Comment 2 Jan Martiska 2015-07-30 12:33:54 UTC
Verified in EAP 6.4.3.CR1.

Comment 3 Petr Penicka 2017-01-17 10:41:17 UTC
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.

Comment 4 Petr Penicka 2017-01-17 10:41:38 UTC
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.

Comment 5 Petr Penicka 2017-01-17 10:43:50 UTC
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.