db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (DERBY-2714) SecureServerTest spends five minutes waiting for a server to start
Date Tue, 29 May 2007 07:56:15 GMT

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

Knut Anders Hatlen resolved DERBY-2714.

       Resolution: Fixed
    Fix Version/s:
       Derby Info:   (was: [Patch Available])

Committed revision 542449.

> 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:
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>            Priority: Minor
>             Fix For:
>         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.

View raw message