Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <13772067.1182177989498.JavaMail.jira@brutus>
Date: Mon, 18 Jun 2007 07:46:29 -0700 (PDT)
From: "Knut Anders Hatlen (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Closed: (DERBY-2714) SecureServerTest spends five minutes
 waiting for a server to start
In-Reply-To: <6914583.1180366875922.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DERBY-2714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Knut Anders Hatlen closed DERBY-2714.
-------------------------------------


> SecureServerTest spends five minutes waiting for a server to start
> ------------------------------------------------------------------
>
>                 Key: DERBY-2714
>                 URL: https://issues.apache.org/jira/browse/DERBY-2714
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.3.0.0
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>            Priority: Minor
>             Fix For: 10.3.0.0
>
>         Attachments: 2714.diff, 2714.stat
>
>
> The first test case in SecureServerTest expects the network server to fail during start-up and tries to ping the server for five minutes before it concludes that the server didn't start. This seems unnecessarily long. If NetworkServerTestSetup.pingForServerStart() had a reference to the Process object for the server process, it could conclude much sooner that the network server process had terminated and would not respond.

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