Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1493898472.1227015464436.JavaMail.jira@brutus>
Date: Tue, 18 Nov 2008 05:37:44 -0800 (PST)
From: "Kathey Marsden (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Resolved: (DERBY-2688) Network server sometimes not
 available when tests in jdbcapi suite is run
In-Reply-To: <16566432.1180011137161.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/DERBY-2688?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kathey Marsden resolved DERBY-2688.
-----------------------------------

    Resolution: Cannot Reproduce

Problem hasn't been seen for some time. Resolving CannotReproduce.


> 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 =C3=98stgaard
>
> Two runs of derbyall on a Suse Linux machine has shown two different test=
s in the jdbcapi part of derbyall failing in the same way, both times run i=
n 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 wi=
th:
> > ERROR 08001: java.net.ConnectException : Error connecting to server xxx=
FILTERED_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. T=
he logs from the derby database seems to either be missing or have been ove=
rwritten by later tests in the same suite.

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