db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1399) DerbyNetAutoStart test fails on JDK 1.6 after introduction JDBC4 driver autoloading
Date Wed, 14 Jun 2006 17:25:30 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1399?page=comments#action_12416229 ] 

Kathey Marsden commented on DERBY-1399:
---------------------------------------

I am very concerned that the patch for this issue is for the test and not the product.  It
is a red flag for me that  existing applications could be impacted by the code change.  

Could you summarize the justification for the test  change to resolve this issue.  



> 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


Mime
View raw message