[
https://issues.apache.org/jira/browse/GEODE-5674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
xiaojian zhou reopened GEODE-5674:
----------------------------------
{noformat}
Reopened as failure is reproduced once during CI:
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/236
> Task :geode-wan:distributedTest
org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderOperationsDUnitTest
> testStartPauseResumeSerialGatewaySender FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.internal.cache.wan.WANTestBase$$Lambda$30/639376949.call in VM
3 running on Host c8495005ff70 with 8 VMs
at org.apache.geode.test.dunit.VM.invoke(VM.java:432)
at org.apache.geode.test.dunit.VM.invoke(VM.java:401)
at org.apache.geode.test.dunit.VM.invoke(VM.java:383)
at
org.apache.geode.internal.cache.wan.WANTestBase.createReceiverInVMs(WANTestBase.java:1984)
at
org.apache.geode.internal.cache.wan.serial.SerialGatewaySenderOperationsDUnitTest.testStartPauseResumeSerialGatewaySender(SerialGatewaySenderOperationsDUnitTest.java:141)
Caused by:
org.apache.geode.internal.cache.wan.GatewayReceiverException: No
available free port found in the given range (23762-23762)
685 tests completed, 1 failed, 60 skipped
> Task :geode-wan:distributedTest FAILED
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-build.276/test-results/distributedTest/1544742490/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Test report artifacts from this job are available at:
http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-build.276/test-artifacts/1544742490/distributedtestfiles-OpenJDK8-1.9.0-build.276.tgz{noformat}
> Stop picking ports randomly for tests
> -------------------------------------
>
> Key: GEODE-5674
> URL: https://issues.apache.org/jira/browse/GEODE-5674
> Project: Geode
> Issue Type: Improvement
> Reporter: Dan Smith
> Assignee: Brian Rowe
> Priority: Major
> Labels: pull-request-available, swat
> Fix For: 1.9.0
>
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> Our tests currently use AvailablePortHelper and AvailablePort to find a
> random port that is not in use.
> However, this can lead to port collisions because after the port is returned,
> it is available until something binds to that socket. In the mean time, other
> calls to getAvailablePort can return the same port, with around 0.01% chance,
> since the range is 10000 ports.
> If we did not pick ports randomly, but instead iterated over a pool of ports,
> we would not return the same port twice until exhaust the pool. We therefore
> not get the same port twice in a test.
> We would need to handle the fact that dunit tests have multiple VMs, so we
> need either a central available port service or a unique pool of ports for
> each process or something like that.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
