You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Julius Stroffek (JIRA)" <ji...@apache.org> on 2007/04/25 15:48:15 UTC

[jira] Updated: (DERBY-2440) DerbyNetNewServer should specify port when it starts a server to avoid requiring 1527 to run

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

Julius Stroffek updated DERBY-2440:
-----------------------------------

    Attachment: d2440.stat
                d2440.diff

Attaching the simple patch. Sorry for the longer delay.

I ran derbyall and suites.All without failures.

Comments welcomed.

> DerbyNetNewServer should specify port when it starts a server to avoid requiring 1527 to run
> --------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2440
>                 URL: https://issues.apache.org/jira/browse/DERBY-2440
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>    Affects Versions: 10.3.0.0
>            Reporter: Dag H. Wanvik
>         Assigned To: Julius Stroffek
>            Priority: Minor
>         Attachments: d2440.diff, d2440.stat
>
>
> To make it possible to run several JUnit tests suites concurrently on 
> the same machine, this test should consult TestConfiguration.getCurrent().getPort()
> when starting the servers.
> DerbyNetNewServer is currently being run as part of NetHarnessJavaTest via
> the old harness adapter HarnessJavaTest.

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