[ http://issues.apache.org/jira/browse/DERBY-1399?page=all ]
Olav Sandstaa updated DERBY-1399:
---------------------------------
Attachment: autoload.diff
This patch fixes the problem with the embedded driver being autoloaded before
all Derby properties have been defined by explicitly unloading the embedded
driver in the start of each sub test.
I have run derbyall on Sun JDK 1.5 and 1.6 with only the usual tests failing.
svn status reports:
M
java/testing/org/apache/derbyTesting/functionTests/tests/derbynet/DerbyNetAutoStart.java
The patch is ready for review and commit.
> DerbyNetAutoStart test fails on JDK 1.6 after introduction JDBC4 driver
> autoloading
> -----------------------------------------------------------------------------------
>
> Key: DERBY-1399
> URL: http://issues.apache.org/jira/browse/DERBY-1399
> Project: Derby
> Type: Bug
> Components: Test
> Versions: 10.2.0.0
> Environment: Sun JDK 1.6
> Reporter: Olav Sandstaa
> Assignee: Olav Sandstaa
> Priority: Minor
> Attachments: autoload.diff
>
> DerbyNetAutoStart.java fails when running on JDK 1.6 with DerbyNet and
> DerbyClient frameworks with the following error:
> Starting test case 1.
> Could not access database through the network server.
> java.net.ConnectException : Error connecting to server localhost on port
> 152
> 7 with message Connection refused.
> Starting test case 2.
> Could not access database through the network server.
> java.net.ConnectException : Error connecting to server localhost on port
> 314
> 15 with message Connection refused.
> Starting test case 3.
> Starting test case 4.
> Starting test case 5.
> FAILED.
> This test seems to have failed consistently since JDBC4 driver autoloading
> was introduced (see DERBY-930).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
