[DERBY-4872] 'No suitable Driver' - Drivers don't get auto-loaded when only derbyrun.jar is in the classpath with ibm 1.6 jvm.

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Invalid
• Affects Version/s: 10.7.1.1
• Component/s: JDBC
• Labels: derby_triage10_8
• Environment: Windows XP, with IBM 1.6 SR8 (and Sun/Oracle's 1.6.0_21-b07 for comparison).
• Urgency: Low
• Issue & fix info: Repro attached
• Assignee: Unassigned
• Reporter: Myrna van Lunteren
• Created: 28/Oct/10 21:30
• Updated: 17/Oct/12 23:12
• Resolved: 16/Mar/11 23:45

Description

With 1.6 jvms, doing DriverManager.getConnection() should autoload all drivers in the classpath. If I understand this correctly, it's based on what's in the manifest.mf, so it makes sense that you'd need to have jars, not just classes in the classpath.

But, with ibm 1.6 jvm, if I have only derbyrun.jar in the classpath, I get the message 'No suitable driver' with both the client, and the embedded driver.
However, if I add derby.jar to the classpath, the error goes away for the embedded driver, and if I add derbyclient.jar, it goes away for the client driver.

Issue Links

• is duplicated by: DERBY-5072 test failure in org.apache.derbyTesting.functionTests.tests.jdbc4.Driver40UnbootedTest.test_notBooted