[
https://issues.apache.org/jira/browse/DERBY-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712673#action_12712673
]
Ole Solberg commented on DERBY-4217:
------------------------------------
I had a look at the replication tests wrt port numbers:
ReplicationRun.initEnvironment() sets
masterServerPort = 1527;
slaveServerPort = 4527;
slaveReplPort = 8888;
With the suggested pattern of system properties (derby.tests.port,
derby.tests.alternativePort, derby.tests.replicationPort) I think we could add
derby.tests.slavePort, and set masterServerPort, slaveServerPort, slaveReplPort
to derby.tests.port, derby.tests.slavePort, derby.tests.replicationPort
respectively.
The masterPortNo set to "test.serverPort" in ReplicationTestRun.suite() should
then be set to derby.tests.port.
It would also be ok, as far as I can see, to use offsets from derby.tests.port
for alternativePort, slavePort and replicationPort, if they are not explicitly
set. Using +1, +2, +3, would then mean that we would need to skip (at least)
three ports when running concurrent tests.
> 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.patch, DERBY-4217.patch, DERBY-4217.patch,
> DERBY-4217.patch, DERBY-4217.stat, DERBY-4217.stat,
> 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.
