db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Created: (DERBY-4480) "No suitable driver found" when attempting to connect while other thread is auto-loading the driver
Date Thu, 17 Dec 2009 17:53:18 GMT
"No suitable driver found" when attempting to connect while other thread is auto-loading the
driver
---------------------------------------------------------------------------------------------------

                 Key: DERBY-4480
                 URL: https://issues.apache.org/jira/browse/DERBY-4480
             Project: Derby
          Issue Type: Bug
          Components: JDBC
    Affects Versions: 10.5.3.0, 10.5.2.0, 10.5.1.1, 10.4.2.0, 10.4.1.3, 10.3.3.0, 10.3.2.1,
10.3.1.4, 10.2.2.0, 10.2.1.6, 10.6.0.0
         Environment: OpenSolaris snv_129, X86
Java(TM) SE Runtime Environment (build 1.6.0_17-b04)
Java(TM) SE Runtime Environment (build 1.7.0-ea-b76)
            Reporter: Knut Anders Hatlen


If you try to connect to embedded Derby from two threads simultaneously, and the embedded
driver has not been loaded yet, one of the threads will trigger auto-loading of the driver
and connect successfully, whereas the other thread will fail with this message: java.sql.SQLException:
No suitable driver found for jdbc:derby:db;create=true

This problem has been present since JDBC 4 auto-loading was implemented (10.2.1.6).

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


Mime
View raw message