You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Anthony Baker (JIRA)" <ji...@apache.org> on 2016/01/15 07:14:48 UTC
[jira] [Closed] (GEODE-163) testPoolLoadAndPeer Cannot create
region with ack because no-ack already exists
[ https://issues.apache.org/jira/browse/GEODE-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anthony Baker closed GEODE-163.
-------------------------------
> testPoolLoadAndPeer Cannot create region with ack because no-ack already exists
> -------------------------------------------------------------------------------
>
> Key: GEODE-163
> URL: https://issues.apache.org/jira/browse/GEODE-163
> Project: Geode
> Issue Type: Bug
> Components: tests
> Reporter: Darrel Schneider
> Priority: Minor
> Fix For: 1.0.0-incubating.M1
>
>
> Probably caused by a previous test leaving the region around as no-ack. Tests should destroy their regions in the test tear down.
> This falure can be found at: https://builds.apache.org/view/All/job/Geode-nightly/166/testReport/com.gemstone.gemfire.cache/ConnectionPoolAndLoaderDUnitTest/testPoolLoadAndPeer/
> dunit.RMIException: While invoking com.gemstone.gemfire.cache.ConnectionPoolAndLoaderDUnitTest$11.call in VM 1 running on Host asf910.gq1.ygridcore.net with 4 VMs
> at dunit.VM.invoke(VM.java:359)
> at dunit.VM.invoke(VM.java:303)
> at dunit.VM.invoke(VM.java:271)
> at com.gemstone.gemfire.cache.ConnectionPoolAndLoaderDUnitTest.testPoolLoadAndPeer(ConnectionPoolAndLoaderDUnitTest.java:288)
> Caused by: java.lang.IllegalStateException: Cannot create region /testPoolLoadAndPeer with DISTRIBUTED_ACK scope because another cache (asf910(3541)<v164>:53941) has same region with DISTRIBUTED_NO_ACK scope.
> at com.gemstone.gemfire.internal.cache.CreateRegionProcessor$CreateRegionMessage.handleCacheDistributionAdvisee(CreateRegionProcessor.java:483)
> at com.gemstone.gemfire.internal.cache.CreateRegionProcessor$CreateRegionMessage.process(CreateRegionProcessor.java:378)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)