You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Dale Emery (Jira)" <ji...@apache.org> on 2021/06/17 23:14:00 UTC

[jira] [Commented] (GEODE-8719) CI Failure: org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest > givenServerCrashesDuringAPPEND_thenDataIsNotLost

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

Dale Emery commented on GEODE-8719:
-----------------------------------

I have a PR that runs distributed tests without the Dockerized test plugin. I’m trying to diagnose a failure in CrashAndNoRepeatDunitTest: http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-6614/test-results/distributedTest/1623867681/

When a server is bounced, it tries bind to the port it was previously bound to, and finds that it’s already bound. After a few hours of trying to find out what other test bound to that port, I now suspect that that the forcibly destroyed process hangs onto the port for a while.

> CI Failure: org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest > givenServerCrashesDuringAPPEND_thenDataIsNotLost
> ---------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-8719
>                 URL: https://issues.apache.org/jira/browse/GEODE-8719
>             Project: Geode
>          Issue Type: Bug
>          Components: redis
>            Reporter: Sarah Abbey
>            Assignee: Jens Deppe
>            Priority: Minor
>             Fix For: 1.14.0
>
>
> CI failure: https://concourse.apachegeode-ci.info/builds/207449
> {code:java}
> org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest > givenServerCrashesDuringAPPEND_thenDataIsNotLost FAILED
>     org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.test.dunit.internal.IdentifiableCallable.call in VM 2 running on Host e0e2f6af9445 with 4 VMs
>         at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:623)
>         at org.apache.geode.test.dunit.VM.invoke(VM.java:460)
>         at org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:268)
>         at org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:261)
>         at org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest.startRedisVM(CrashAndNoRepeatDUnitTest.java:131)
>         at org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest.givenServerCrashesDuringAPPEND_thenDataIsNotLost(CrashAndNoRepeatDUnitTest.java:164)        Caused by:
>         org.apache.geode.management.ManagementException: Could not start Redis Server using bind address: localhost/127.0.0.1 and port: 44579. Please make sure nothing else is running on this address/port combination.            Caused by:
>             java.net.BindException: Address already in use
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)