Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-4872

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

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Invalid
    • Affects Version/s: 10.7.1.1
    • Fix Version/s: None
    • Component/s: JDBC
    • 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

      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.

        Attachments

        1. ReproDerby4872.java
          2 kB
          Myrna van Lunteren
        2. ReproDerby4872.java
          0.5 kB
          Myrna van Lunteren

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                myrna Myrna van Lunteren
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: