db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steven Hendrickx (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-5096) DisconnectException: "Connection was refused because the database DB was not found" on OS/400
Date Mon, 07 Mar 2011 15:10:59 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13003383#comment-13003383

Steven Hendrickx commented on DERBY-5096:

Mind, since this is a SQLNonTransientConnectionException, we cannot retry to create the connection.

> DisconnectException: "Connection was refused because the database DB was not found" on
> ---------------------------------------------------------------------------------------------
>                 Key: DERBY-5096
>                 URL: https://issues.apache.org/jira/browse/DERBY-5096
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Server
>    Affects Versions:
>         Environment: System: OS/400 V7R1M0 on PowerPC; JVM: IBM J9 VM 2.4 (continuously
> Probably Windows 7 64 bit with Sun VM (1.6) too (but not reproduced)
>            Reporter: Steven Hendrickx
>         Attachments: getconnection_reproduce.zip
> A process starts derby as network server (new NetworkServerControl, start) and waits
for derby to respond (retry ping until success). After the server has started, the same process
makes a connection with DriverManager.getConnection().
> The first time this process runs, this will always fail with  "SQLNonTransientConnectionException:
The connection was refused because the database Flows;create=true was not found." However,
at the same time, "derby.log" and "Flows" directory are created in the derby home. The "Flows"
directory contains "log", "seg0", "tmp", "db.lck", "service.properties", etc ...
> The second time the process is started, the connection will succeed and the "Flows" database
can be used successfully.
> The attachment contains a Java program (DerbyGetConnection.java) that reproduces this
problem consistently on our OS/400 V7R1M0 with IBM J9 VM. Probably this may happen on other
systems too (Win7), but we were unable to reproduce it there (on my machine with Win7, this
same program ran successful every run; might be a threading or I/O issue that occurs easily
on slower hardware?).
> The attachment contains also derby tracing ("derby.drda.traceAll") and logging/tracing
of the DriverManager.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message