[jira] [Resolved] (GEODE-180) SnapshotDUnitTest intermittently fails because of a cache left over from a previous test
[ https://issues.apache.org/jira/browse/GEODE-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider resolved GEODE-180. Resolution: Fixed This issue was resolved by when the earlier test was fixed SnapshotDUnitTest intermittently fails because of a cache left over from a previous test Key: GEODE-180 URL: https://issues.apache.org/jira/browse/GEODE-180 Project: Geode Issue Type: Bug Components: tests Reporter: Darrel Schneider Priority: Minor See: https://builds.apache.org/view/All/job/Geode-nightly/172/testReport/com.gemstone.gemfire.cache.snapshot/SnapshotDUnitTest/testCacheExportFilterException/ Multiple methods on this test fail with the same error. Here is one: SnapshotDUnitTest.testCacheExportFilterException ava.lang.IllegalStateException: Cannot create region /PdxTypes DataPolicy withPersistence=true because another cache (asf903(24154)v619:34023) has the same region DataPolicy withPersistence=false. Persistent members must be started before non-persistent members at com.gemstone.gemfire.internal.cache.CreateRegionProcessor$CreateRegionMessage.handleCacheDistributionAdvisee(CreateRegionProcessor.java:483) at com.gemstone.gemfire.internal.cache.CreateRegionProcessor$CreateRegionMessage.process(CreateRegionProcessor.java:378) at com.gemstone.gemfire.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:371) at com.gemstone.gemfire.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:442) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at com.gemstone.gemfire.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:692) at com.gemstone.gemfire.distributed.internal.DistributionManager$5$1.run(DistributionManager.java:1000) at java.lang.Thread.run(Thread.java:745) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (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 ] Darrel Schneider resolved GEODE-163. Resolution: Fixed The other test was fixed which resolved this issue 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 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)
[jira] [Updated] (GEODE-164) launcher junit tests failing because working directory does not exist
[ https://issues.apache.org/jira/browse/GEODE-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider updated GEODE-164: --- Component/s: tests launcher junit tests failing because working directory does not exist - Key: GEODE-164 URL: https://issues.apache.org/jira/browse/GEODE-164 Project: Geode Issue Type: Bug Components: tests Reporter: Darrel Schneider Priority: Minor First seen in build #166. https://builds.apache.org/view/All/job/Geode-nightly/166/testReport/junit/com.gemstone.gemfire.distributed/LocatorLauncherJUnitTest/testBuild/ java.lang.IllegalArgumentException: The working directory for the Locator could not be found. at com.gemstone.gemfire.distributed.LocatorLauncher$Builder.setWorkingDirectory(LocatorLauncher.java:1656) at com.gemstone.gemfire.distributed.LocatorLauncherJUnitTest.testBuild(LocatorLauncherJUnitTest.java:360) Caused by: java.io.FileNotFoundException: /tmp/junit1625423486198578553 ... 46 more The tests that failed with what looks like the same problem are: -- com.gemstone.gemfire.distributed.LocatorLauncherJUnitTest.testBuild -- com.gemstone.gemfire.distributed.LocatorLauncherJUnitTest.testSetAndGetWorkingDirectory -- com.gemstone.gemfire.distributed.ServerLauncherJUnitTest.testParseArguments -- com.gemstone.gemfire.distributed.ServerLauncherJUnitTest.testSetAndGetWorkingDirectory -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (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 ] Darrel Schneider updated GEODE-163: --- Component/s: tests 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 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)
[jira] [Commented] (GEODE-17) Provide Integrated Security
[ https://issues.apache.org/jira/browse/GEODE-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14693928#comment-14693928 ] Nilkanth Patel commented on GEODE-17: - is requirement for this feature changed..? I think, Initially it was designed with the consideration that we should not change existing security C/S interfaces, rather utilizing the same for other non-secure channels. Is changes to public security interfaces are now in scope? Provide Integrated Security --- Key: GEODE-17 URL: https://issues.apache.org/jira/browse/GEODE-17 Project: Geode Issue Type: New Feature Components: client/server, core, management tools Reporter: Tushar Khairnar Assignee: Tushar Khairnar Labels: security Integrated Security: Purpose of integrated security feature is to provide uniform authentication and authorization capabilities for all Geode clients. Geode distributed systems has different clients, some perform cache/region operations, some perform management operations. In order to authenticate and authorize these actions we need single consistent framework or interface. Such interface should allow configuration of access levels from single place and/or repository. The key requirements being met here are - Authentication of all clients from single plugin - Authorization of cache/data operations (through cache-client and REST) and managements (GFSH/JMX) operations from single plugin - Extend existing Client-Server security framework -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-212) ResourceManager implementation impacts off-heap performance
Darrel Schneider created GEODE-212: -- Summary: ResourceManager implementation impacts off-heap performance Key: GEODE-212 URL: https://issues.apache.org/jira/browse/GEODE-212 Project: Geode Issue Type: Bug Components: offheap Reporter: Darrel Schneider Assignee: Darrel Schneider When the resource manager is configured with either a eviction or critical threshold then it registers a listener with the off-heap SimpleMemoryAllocator that causes every off-heap allocate and free to call this listener. The current listener does a synchronize on a singleton and notifies it. This will impact the rate at which multiple threads can allocate and free off-heap objects. I simple test using 8 threads showed that without the resource manager they could do 16 million allocate/frees in 3 seconds. With the resource manager it took 12 seconds. The notify is done to a singleton thread that simple checks to see if the new off-heap memory size would result in a change to the resource manager state. This can be done without synchronizing. Only if a change is possible do we need to do the sync and notify. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-211) ConcurrentRegionOperationsJUnitTest takes too long to run
[ https://issues.apache.org/jira/browse/GEODE-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider resolved GEODE-211. Resolution: Fixed ConcurrentRegionOperationsJUnitTest takes too long to run - Key: GEODE-211 URL: https://issues.apache.org/jira/browse/GEODE-211 Project: Geode Issue Type: Bug Components: tests Reporter: Darrel Schneider Assignee: Darrel Schneider Priority: Minor Original Estimate: 1h Remaining Estimate: 1h ConcurrentRegionOperationsJUnitTest takes over 200 seconds to run. A couple of simple changes can cut this time in half. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-209) FailWithTimeoutOfWaitForOutputToMatchJUnitTest.testFailWithTimeoutOfWaitForOutputToMatch is not stable
[
https://issues.apache.org/jira/browse/GEODE-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashvin updated GEODE-209:
-
Assignee: Kirk Lund
FailWithTimeoutOfWaitForOutputToMatchJUnitTest.testFailWithTimeoutOfWaitForOutputToMatch
is not stable
--
Key: GEODE-209
URL: https://issues.apache.org/jira/browse/GEODE-209
Project: Geode
Issue Type: Bug
Affects Versions: 1.0.0-incubating
Reporter: Ashvin
Assignee: Kirk Lund
Priority: Minor
FailWithTimeoutOfWaitForOutputToMatchJUnitTest.testFailWithTimeoutOfWaitForOutputToMatch
failed 5 times in the last 30 runs. It is failing in the tearDown phase.
{quote}
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertFalse(Assert.java:64)
at org.junit.Assert.assertFalse(Assert.java:74)
at
com.gemstone.gemfire.test.golden.FailWithTimeoutOfWaitForOutputToMatchJUnitTest.subTearDown(FailWithTimeoutOfWaitForOutputToMatchJUnitTest.java:20)
at
com.gemstone.gemfire.test.golden.GoldenTestCase.tearDownGoldenTest(GoldenTestCase.java:49)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
{quote}
{code}
public void subTearDown() throws Exception {
this.process.waitFor();
assertFalse(this.process.isAlive());
}
{code}
Fix to GEODE-127 may have caused this issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (GEODE-211) ConcurrentRegionOperationsJUnitTest takes too long to run
[ https://issues.apache.org/jira/browse/GEODE-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14693913#comment-14693913 ] ASF subversion and git services commented on GEODE-211: --- Commit 9de95d63275c5e5a13b35d5bb7744c399916d7f5 in incubator-geode's branch refs/heads/develop from [~dschneider] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=9de95d6 ] GEODE-211: shorten the time ConcurrentRegionOperationsJUnitTest runs ConcurrentRegionOperationsJUnitTest takes too long to run - Key: GEODE-211 URL: https://issues.apache.org/jira/browse/GEODE-211 Project: Geode Issue Type: Bug Components: tests Reporter: Darrel Schneider Assignee: Darrel Schneider Priority: Minor Original Estimate: 1h Remaining Estimate: 1h ConcurrentRegionOperationsJUnitTest takes over 200 seconds to run. A couple of simple changes can cut this time in half. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
