Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <28845236.1155505514817.JavaMail.jira@brutus>
Date: Sun, 13 Aug 2006 14:45:14 -0700 (PDT)
From: "Kathey Marsden (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_12427782 ] 
            
Kathey Marsden commented on DERBY-1399:
---------------------------------------

Is this patch still needed, now that DERBY-1459 is fixed?  Would it be ok to uncheck patch available?


> 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
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.2.0.0
>         Environment: Sun JDK 1.6
>            Reporter: Olav Sandstaa
>         Assigned To: 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