[
https://issues.apache.org/jira/browse/DERBY-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718950#action_12718950
]
Tiago R. Espinha commented on DERBY-4217:
-----------------------------------------
Regarding my comment on 09/Jun/09 10:45 AM, there has been another change here.
At this point, the pings under NetworkServerControlClientCommandTest that don't
specify a port through the -p parameter won't be ran if the current port is
different from the DEFAULT_PORT in TestConfiguration. The portless pings go to
the 1527 port by default so it makes no sense to ping this port if we are using
a different one.
It needs to be noted that the possibility of asserting a failed ping would be a
good option but it isn't quite viable. The ping is a 'blind' operation, meaning
that whichever program binds the port being pinged, the ping will pass. My
suites.All run with a custom port and with an application binding on to 1527
would fail with this option.
> Make the default port for the suites.All run configurable with a system
> property.
> ---------------------------------------------------------------------------------
>
> Key: DERBY-4217
> URL: https://issues.apache.org/jira/browse/DERBY-4217
> Project: Derby
> Issue Type: Sub-task
> Affects Versions: 10.6.0.0
> Reporter: Tiago R. Espinha
> Assignee: Tiago R. Espinha
> Attachments: DERBY-4217-dtp.patch, DERBY-4217-dtp.patch,
> DERBY-4217-dtp.patch, DERBY-4217-dtp.patch, DERBY-4217-ij.patch,
> DERBY-4217-ij.patch, DERBY-4217-ij.patch, DERBY-4217-ij.patch,
> DERBY-4217-ij.patch, DERBY-4217-ij.stat, DERBY-4217-ij.stat,
> DERBY-4217.patch, DERBY-4217.patch, DERBY-4217.patch, DERBY-4217.patch,
> DERBY-4217.stat, DERBY-4217.stat, ErrorLog_suitesAll_bound.tgz,
> ReproNetworkServerControl.java
>
>
> The goal is to make the port used for suites.All configurable through a
> system property passed on to the JVM.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
