[
https://issues.apache.org/jira/browse/GEODE-8772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17246698#comment-17246698
]
ASF subversion and git services commented on GEODE-8772:
--------------------------------------------------------
Commit 160847e56d4d09b641093980ef7add3d969bfdb9 in geode's branch
refs/heads/develop from Dale Emery
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=160847e ]
GEODE-8772: Launcher rule assigns available ports (#5827)
LocatorLauncherStartupRule now assigns available HTTP and JMX ports rather than
launching with the product's default ports. Assigning available ports reduces
bind conflicts when the tests that use this rule run in parallel outside of
Docker.
> Avoid using default ports in tests
> ----------------------------------
>
> Key: GEODE-8772
> URL: https://issues.apache.org/jira/browse/GEODE-8772
> Project: Geode
> Issue Type: Test
> Components: tests
> Affects Versions: 1.14.0
> Reporter: Dale Emery
> Assignee: Dale Emery
> Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
>
> Many distributed tests and upgrade tests (and sometimes others) launch
> members with default ports, especially for JMX (1099) and HTTP service
> (7070). When run in parallel outside of docker, these tests often fail
> because the default port is already in use in another test.
> Except when specifically testing the product's use of the defaults, every
> test should assign ports known to be available. For many tests, we can
> accomplish this by changing the test framework to assign available ports.
> Other tests may require changes in the test code.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
