commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Krasimir Nedkov (JIRA)" <>
Subject [jira] Created: (DBCP-333) Unable to create a JDBC driver using custom class loader
Date Tue, 04 May 2010 12:08:56 GMT
Unable to create a JDBC driver using custom class loader

                 Key: DBCP-333
             Project: Commons Dbcp
          Issue Type: Bug
    Affects Versions: 1.3
            Reporter: Krasimir Nedkov


I'm unable to instantiate my JDBC driver using a custom class loader:
        BasicDataSource ds = new BasicDataSource();
        String connectURL = "jdbc:mysql://"+config.getHost()+"/"+config.getDatabaseName();

Having a look at the org.apache.commons.dbcp.BasicDataSource.createConnectionFactory() method
implementation, I found that the class loader is actually ignored. In the first part of the
method there is an attempt to load the class that seems to pass successfully, but the loaded
class is not assigned to the driverFromCCL variable:
            if (driverClassLoader == null) {
            } else {
                 Class.forName(driverClassName, true, driverClassLoader);

Then in the second part of the method driverFromCCL is still null and instead of instantiating
the driver directly, DriverManager.getDriver(url) is called, which fails:
            if (driverFromCCL == null) {
                driver = DriverManager.getDriver(url);
            } else {
                // Usage of DriverManager is not possible, as it does not
                // respect the ContextClassLoader
                driver = (Driver) driverFromCCL.newInstance();
                if (!driver.acceptsURL(url)) {
                    throw new SQLException("No suitable driver", "08001"); 

Kind regards,

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message