Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <2130644345.1246405128398.JavaMail.jira@brutus>
Date: Tue, 30 Jun 2009 16:38:48 -0700 (PDT)
From: "Dag H. Wanvik (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-1794) Should create a test that verifies
 acceptable performance of network server startup
In-Reply-To: <3725789.1157053642271.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-1794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dag H. Wanvik updated DERBY-1794:
---------------------------------

    Issue Type: Improvement  (was: Test)

> Should create a test that verifies acceptable performance of network server startup
> -----------------------------------------------------------------------------------
>
>                 Key: DERBY-1794
>                 URL: https://issues.apache.org/jira/browse/DERBY-1794
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>    Affects Versions: 10.3.1.4
>            Reporter: Mike Matrigali
>
> A number of tests in the regression suite rely on starting up a network server and subsequently connecting to it.  Each tends to have some sort of "wait" mechanism and may fail if the wait is "too" long.   It is often sort of cryptic to tell why these tests have failed if the real reason is the network server did not start in a reasonable amount of time.  It would be good to develop a test that specifically looked at network server start up time and verified from release to release that it was behaving correctly.

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