You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Bruce Schuchardt (JIRA)" <ji...@apache.org> on 2016/08/03 16:47:20 UTC

[jira] [Commented] (GEODE-1722) Distributed tests should use a restricted membership-port-range

    [ https://issues.apache.org/jira/browse/GEODE-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15406192#comment-15406192 ] 

Bruce Schuchardt commented on GEODE-1722:
-----------------------------------------

fixed in b81ebccba3a39647b020ac8d4ee2bf5b993c2356
DistributionConfig now restricts the port range when running under DUnitLauncher to use ports outside of the pool used by AvailablePort and AvailablePortHelper.

> Distributed tests should use a restricted membership-port-range
> ---------------------------------------------------------------
>
>                 Key: GEODE-1722
>                 URL: https://issues.apache.org/jira/browse/GEODE-1722
>             Project: Geode
>          Issue Type: Improvement
>            Reporter: Bruce Schuchardt
>            Assignee: Bruce Schuchardt
>
> Distributed unit tests are using a membership-port-range that includes the pool of port numbers used by AvailablePort and AvailablePortHelper.  Since most tests grab available port during set-up and then create caches this makes it possible for the caches to grab the "available" ports and cause the test to fail when the test tells a cache-server or other component to use the ports returned by AvailablePort or AvailablePortHelper.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)