You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Mark Hanson (Jira)" <ji...@apache.org> on 2019/12/30 18:52:08 UTC

[jira] [Closed] (GEODE-6681) [CI Failure] CreateGatewayReceiverCommandDUnitTest > twoGatewayReceiversCannotCoexist

     [ https://issues.apache.org/jira/browse/GEODE-6681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Hanson closed GEODE-6681.
------------------------------

Transition from Resolved to Closed for Apache Geode 1.11.0 RC4 release.

> [CI Failure] CreateGatewayReceiverCommandDUnitTest > twoGatewayReceiversCannotCoexist
> -------------------------------------------------------------------------------------
>
>                 Key: GEODE-6681
>                 URL: https://issues.apache.org/jira/browse/GEODE-6681
>             Project: Geode
>          Issue Type: Bug
>          Components: wan
>            Reporter: Nabarun Nag
>            Assignee: Kirk Lund
>            Priority: Major
>             Fix For: 1.11.0
>
>
> *CI Failure located at* - [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/645]
> *Maybe*
>  Possible issue may be monitoring region is being accessed while the test is being simultaneously being shut down (leading to closing of the regions)
>  Similar tickets have been solved for other tests.
>   
>  *Stacktrace*
> {noformat}
> org.apache.geode.internal.cache.wan.wancommand.CreateGatewayReceiverCommandDUnitTest > twoGatewayReceiversCannotCoexist FAILED
>  java.lang.AssertionError: Suspicious strings were written to the log during this run.
>  Fix the strings or use IgnoredException.addIgnoredException to ignore.
>  -----------------------------------------------------------------------
>  Found suspect string in log4j at line 1245
>  
>  [fatal 2019/04/19 17:56:13.894 UTC <FederatingManager2> tid=1578] Uncaught exception in thread Thread[FederatingManager2,5,RMI Runtime]
>  org.apache.geode.cache.RegionDestroyedException: org.apache.geode.internal.cache.DistributedRegion[path='/_monitoringRegion_172.17.0.17<v1>41002';scope=DISTRIBUTED_NO_ACK';dataPolicy=REPLICATE]
>  at org.apache.geode.internal.cache.LocalRegion.checkRegionDestroyed(LocalRegion.java:7420)
>  at org.apache.geode.internal.cache.LocalRegion.checkReadiness(LocalRegion.java:2814)
>  at org.apache.geode.internal.cache.LocalRegion.entrySet(LocalRegion.java:1948)
>  at org.apache.geode.internal.cache.LocalRegion.entrySet(LocalRegion.java:8463)
>  at org.apache.geode.management.internal.MBeanProxyFactory.removeAllProxies(MBeanProxyFactory.java:153)
>  at org.apache.geode.management.internal.FederatingManager.removeMemberArtifacts(FederatingManager.java:212)
>  at org.apache.geode.management.internal.FederatingManager.access$000(FederatingManager.java:64)
>  at org.apache.geode.management.internal.FederatingManager$RemoveMemberTask.run(FederatingManager.java:313)
>  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>  at java.lang.Thread.run(Thread.java:748)
> {noformat}



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