db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vemund Østgaard (JIRA) <j...@apache.org>
Subject [jira] Created: (DERBY-2688) Network server sometimes not available when tests in jdbcapi suite is run
Date Thu, 24 May 2007 12:52:17 GMT
Network server sometimes not available when tests in jdbcapi suite is run
-------------------------------------------------------------------------

                 Key: DERBY-2688
                 URL: https://issues.apache.org/jira/browse/DERBY-2688
             Project: Derby
          Issue Type: Bug
          Components: Test
    Affects Versions: 10.2.2.1
         Environment: Suse Linux Enterprise Server 10, Linux 2.6.16.21-0.8-smp
Java HotSpot(TM) Server VM (build 1.5.0_07-b03, mixed mode)

            Reporter: Vemund Østgaard


Two runs of derbyall on a Suse Linux machine has shown two different tests in the jdbcapi
part of derbyall failing in the same way, both times run in the derbynetclient framework.
It seems that when the test is executed it expects a network server to allready have been
started at "localhost", but this is probably not the case as the tests fail from the first
statement with:

> ERROR 08001: java.net.ConnectException : Error connecting to server xxxFILTERED_HOSTNAMExxx
on port 1527 with message Connection refused.
28a30
> IJ ERROR: Unable to establish connection
29a32
> IJ ERROR: Unable to establish connection
31 del

...

There are no logs available from the code that starts the network server, which might have
shown the cause of why it (most likely) is not running. The logs from the derby database seems
to either be missing or have been overwritten by later tests in the same suite.


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message