[jira] Updated: (DERBY-2714) SecureServerTest spends five minutes waiting for a server to start

["Knut Anders Hatlen (JIRA)" <ji...@apache.org>]

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

Knut Anders Hatlen updated DERBY-2714:
--------------------------------------

    Attachment: 2714.stat
                2714.diff

The attached patch reduces the time required to run SecureServerTest on my machine from 5 minutes 8 seconds to about 8 seconds. It makes pingForServerStart() check the status of the server process and stop pinging it if it's dead. I'm running suites.All with it now.

> 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
>         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.