DerbyNetNewServer should specify port when it starts a server to
avoid requiring 1527 to run
In-Reply-To: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
[
https://issues.apache.org/jira/browse/DERBY-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dag H. Wanvik updated DERBY-2440:
---------------------------------
Summary:
A connection attempt by an unauthorized user leaves a previously non-booted
database booted
DerbyNetNewServer should specify port when it starts a server to avoid
requiring 1527 to run
was:
DerbyNetNewServer run from
DerbyNetNewServer should specify port when it starts a server to avoid
requiring 1527 to run
> A connection attempt by an unauthorized user leaves a previously non-booted
> database booted
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
> Priority: Minor
>
> 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.
