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 "Dag H. Wanvik (JIRA)" <ji...@apache.org> on 2007/04/26 00:04:34 UTC

[jira] Commented: (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:comment-tabpanel#action_12491812 ] 

Dag H. Wanvik commented on DERBY-2440:
--------------------------------------

+1
I modified TestConfiguration.DEFAULT_PORT temporarily and ran the test
standalone as a harness test and as JUnit (part of NetHarnessJavaTest) and both
worked as expected.

I also ran regression tests successfully again.

Committed as svn 532498. Thanks for fixing this, Julius!


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