[DERBY-1399] DerbyNetAutoStart test fails on JDK 1.6 after introduction JDBC4 driver autoloading

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 10.2.1.6
• Fix Version/s: 10.2.1.6
• Component/s: Test
• Environment: Sun JDK 1.6
• Assignee: Olav Sandstaa
• Reporter: Olav Sandstaa
• Created: 13/Jun/06 19:24
• Updated: 21/Jan/11 18:09
• Resolved: 14/Aug/06 10:40

Description

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).

Issue Links

• is related to: DERBY-1429 Additional vulnerability to non-deterministic startup behavior when applications generate derby properties on the fly