Bug 1007181
Summary: | [GSS] (6.2.x) testConnection should account for deployment classloader | |||
---|---|---|---|---|
Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Jay SenSharma <jsenshar> | |
Component: | Class Loading | Assignee: | Jay SenSharma <jsenshar> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | ||
Severity: | medium | Docs Contact: | Russell Dickenson <rdickens> | |
Priority: | medium | |||
Version: | 6.1.1 | CC: | bmaxwell, cdewolf, david.lloyd, dereed, jawilson, jmartisk, jolee, jsenshar, myarboro, rajanikanth, sappleto, sjadhav, smumford | |
Target Milestone: | CR2 | |||
Target Release: | EAP 6.2.2 | |||
Hardware: | All | |||
OS: | All | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: |
A bug was uncovered that could cause earlier versions of JBoss EAP to throw an exception when testing a datasource.
The exception presented while using the LDAP protocol in the datasource "connection-url" tag. The product was failing to instantiate +InitialContextFactory+ because the "org.jboss.as.connector" module was not able to access some of the JDK provided classes (such as +com.sun.jndi.ldap.LdapCtxFactory+). This resulted in a datasource connection test failure when the Datasource "connection-url" was using "ldap://" protocol.
This issue was resolved by adding a dependency on +sun.jdk+ to the +org.jboss.as.connector+ module. This makes the required JDK classes accessible from the connector module and the datasource testing using CLI using "test-connection-in-pool" operation succeeds.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1060997 (view as bug list) | Environment: | ||
Last Closed: | 2014-06-02 12:49:37 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: | 1060997 | |||
Bug Blocks: | 1049365 |
Description
Jay SenSharma
2013-09-12 04:59:26 UTC
Workaround : ############ Add the module dependency "$JBOSS_HOME/modules/system/layers/base/org/jboss/as/connector/main/module.xml"" which needs to be dependent on the following module <module name="sun.jdk"/> - So alter the module "org.jboss.as.connector" and add the following dependencies to it : <dependencies> <module name="sun.jdk"/> . . . </dependencies> Jesper Pedersen <jpederse> made a comment on jira WFLY-2047 Why is LDAP leaking into JDBC ? Jesper Pedersen <jpederse> made a comment on jira WFLY-2047 [~darranl] Do you have input on this ? Darran Lofthouse <darran.lofthouse> made a comment on jira WFLY-2047 Hi Jesper, As this is how the Oracle connection is defined shouldn't it be the Oracle driver that has the dependency on sun.jdk ? Jesper Pedersen <jpederse> updated the status of jira WFLY-2047 to Closed Jesper Pedersen <jpederse> made a comment on jira WFLY-2047 See [~dlofthouse] 's comment - it is the Oracle module that needs the dependency if ldap is used in the url Jay Kumar SenSharma <jsenshar> made a comment on jira WFLY-2047 Oracle Module has the following dependency still the same issue occurs. Jay Kumar SenSharma <jsenshar> made a comment on jira WFLY-2047 Oracle Module has the following dependency still the same issue occurs. Jay Kumar SenSharma <jsenshar> made a comment on jira WFLY-2047 <?xml version="1.0" ?> <module xmlns="urn:jboss:module:1.1" name="com.oracle.jdbc6"> <resources> <resource-root path="ojdbc6.jar"/> </resources> <dependencies> <module name="javax.api"/> <module name="sun.jdk"/> </dependencies> </module> Jesper Pedersen <jpederse> made a comment on jira WFLY-2047 Then it is a classloading or module dependency issue Jay Kumar SenSharma <jsenshar> updated the status of jira WFLY-2047 to Reopened Jay Kumar SenSharma <jsenshar> made a comment on jira WFLY-2047 Reopening this issue and will try to change the component to Jboss classloading Jesper Pedersen <jpederse> made a comment on jira WFLY-2047 Changed the description to account for the real failure `Requires doc text` flag cleared as it's too late to include an entry in the JBoss EAP 6.2.0 Release Notes. The customer has asked if they can test this - can the fix be made available as a patch? Redrafted Doc Text to prose format. Verified in 6.2.2.CR2. Stefano Maestri <smaestri> updated the status of jira WFLY-2047 to Closed |