[ https://issues.apache.org/jira/browse/GEODE-9495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17416870#comment-17416870 ]
Geode Integration commented on GEODE-9495: ------------------------------------------ Seen in [acceptance-test-openjdk8 #193|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/acceptance-test-openjdk8/builds/193] ... see [test results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0495/test-results/acceptanceTest/1631845462/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0495/test-artifacts/1631845462/acceptancetestfiles-openjdk8-1.15.0-build.0495.tgz]. > remove thread sleep from PubSubNativeRedisAcceptanceTest class cleanup > ---------------------------------------------------------------------- > > Key: GEODE-9495 > URL: https://issues.apache.org/jira/browse/GEODE-9495 > Project: Geode > Issue Type: Improvement > Components: redis > Affects Versions: 1.15.0 > Reporter: Hale Bales > Assignee: Ray Ingles > Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > GEODE-9338 includes the addition of a Thread.sleep(240000) in the class > cleanup. This wait is necessary to allow the sockets used in this class to > exit the TIME_WAIT state. Out of Mac, Linux, and Windows, Windows has the > longest default TIME_WAIT, which is 240 seconds. So currently at the end of > the PubSubNativeRedisAcceptanceTest tests, we wait for 240 seconds. > Another solution was proposed that involved parsing netstat outputs to find > out when enough sockets have been freed, but the complexity didn't buy us > much there. > A potential other solution would be to reduce the TIME_WAIT period when > running the tests in CI. > If we don't wait for the TIME_WAIT period to be up then other tests being run > after it will get bind exceptions. -- This message was sent by Atlassian Jira (v8.3.4#803005)