[
https://issues.apache.org/jira/browse/DERBY-4480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13483349#comment-13483349
]
Knut Anders Hatlen commented on DERBY-4480:
-------------------------------------------
I ran with jars, since auto-loading does not work when running from classes. I
only had derby.jar in the classpath.
I'm not sure if it's a JVM bug or if it's a problem in Derby's engine boot code
that gets triggered by the way that version of the JVM invokes it. I'll try to
pinpoint exactly what is causing it and what has changed. Should probably also
add a regression test case too before closing the issue.
> "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.2.1.6, 10.2.2.0, 10.3.1.4, 10.3.2.1, 10.3.3.0,
> 10.4.1.3, 10.4.2.0, 10.5.1.1, 10.5.2.0, 10.5.3.0, 10.6.1.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
> Labels: derby_triage10_8
> Attachments: AutoloadTest.java
>
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
