Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <28761731.1150219170703.JavaMail.jira@brutus>
Date: Tue, 13 Jun 2006 17:19:30 +0000 (GMT+00:00)
From: "Olav Sandstaa (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-1399) DerbyNetAutoStart test fails on JDK
 1.6 after introduction JDBC4 driver autoloading
In-Reply-To: <11283835.1150201529859.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/DERBY-1399?page=comments#action_12416036 ] 

Olav Sandstaa commented on DERBY-1399:
--------------------------------------

This problem is similar to the problem that caused the NIST tests to
fail when running with JDK 1.6 (see DERBY-1379).

The DerbyNetAutoStart test does the following during start up:

 1. Explicitly load the DerbyNetClient by calling
    TestUtil.loadDriver(). Due to JDBC driver autoloading, this will
    also load the embedded JDBC driver and the Derby engine when
    running with JDK 1.6.

 2. Set some properties for the embedded driver. In the first test
    case this property is:

     derby.drda.startNetworkServer=true

    to make the network server start as part of loading the embedded driver.

 3. Explicitly load the embedded driver. But since the driver and
    engine are already loaded, not much is done here. As a
    consequence the properties set does not take effect, and the
    network server is not started. This makes the test fail.

I plan to fix this problem by explicitly attempt to unload the
embedded driver and engine in the start of each individual subtest. 
(This is already done after each sub test has run, but this does not
help the first subtest).


> 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

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