C3P0ConnectionProvider ---------------------- Key: HHH-6413 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6413 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.6.4 Environment: c3p0-0.9.1.2 com.p6spy.engine.spy.P6SpyDriver, oracle.jdbc.driver.OracleDriver, i.e. more than one driver suited to resolve a jdbc url matching jdbc:oracle:thin:@<host>:<port>:<sid> Reporter: Robert Saenger Priority: Critical org.hibernate.connection.C3P0ConnectionProvider.configure does not effectively pass the jdbcDriverClass driver configuration to C3P0. Unfortunately it is not sufficient to ensure loading of the given class, since C3P0 reads the driver class from property c3p0.driverClass, which is not set by C3P0ConnectionProvider. If the c3p0.driverClass defaults to null, com.mchange.v2.c3p0.DriverManagerDataSource.driver() delegates the determination of an appropriate driver to java.sql.DriverManager, which attempts to select an appropriate driver from the set of registered JDBC drivers. If more than one appropriate driver has been registered, that understands a given URL it might happen, that not the intended driver is used (although C3P0ConnectionProvider log info message has stated it is being used). However, even if C3P0ConnectionProvider would accurately pass down the jdbcDriverClass to C3P0, the latest c3p0 (0.9.1.2) would not handle it appropriately. See also dependent bug http://sourceforge.net/tracker/?func=detail&aid=3357654&group_id=.... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira