[jira] [Updated] (GEODE-1619) CI failure: PartitionedRegionSingleHopWithServerGroupDUnitTest.test_SingleHopWithServerGroupTwoClientServerGroup
[
https://issues.apache.org/jira/browse/GEODE-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Schuchardt updated GEODE-1619:
Summary: CI failure:
PartitionedRegionSingleHopWithServerGroupDUnitTest.test_SingleHopWithServerGroupTwoClientServerGroup
(was:
PartitionedRegionSingleHopWithServerGroupDUnitTest.test_SingleHopWithServerGroupTwoClientServerGroup)
> CI failure:
> PartitionedRegionSingleHopWithServerGroupDUnitTest.test_SingleHopWithServerGroupTwoClientServerGroup
>
>
> Key: GEODE-1619
> URL: https://issues.apache.org/jira/browse/GEODE-1619
> Project: Geode
> Issue Type: Bug
> Components: client/server
>Reporter: Dan Smith
> Labels: ci
>
> {noformat}
> com.gemstone.gemfire.test.dunit.RMIException: While invoking
> com.gemstone.gemfire.internal.cache.PartitionedRegionSingleHopWithServerGroupDUnitTest$$Lambda$103/472208708.run
> in VM 2 running on Host rooktwo.gemstone.com with 4 VMs
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:389)
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:355)
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:293)
> at
> com.gemstone.gemfire.internal.cache.PartitionedRegionSingleHopWithServerGroupDUnitTest.test_SingleHopWithServerGroupTwoClientServerGroup(PartitionedRegionSingleHopWithServerGroupDUnitTest.java:398)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.i
[jira] [Updated] (GEODE-1703) CI failure: PersistentRecoveryOrderDUnitTest.testCrashDuringPreparePersistentId fails assertion: Region not created within30000
[
https://issues.apache.org/jira/browse/GEODE-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-1703:
-
Labels: flaky (was: )
> CI failure:
> PersistentRecoveryOrderDUnitTest.testCrashDuringPreparePersistentId fails
> assertion: Region not created within3
> ---
>
> Key: GEODE-1703
> URL: https://issues.apache.org/jira/browse/GEODE-1703
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Kirk Lund
> Labels: flaky
>
> {noformat}
> :geode-core:distributedTest
> com.gemstone.gemfire.internal.cache.persistence.PersistentRecoveryOrderDUnitTest
> > testCrashDuringPreparePersistentId FAILED
> java.lang.AssertionError: Region not created within3
> at org.junit.Assert.fail(Assert.java:88)
> at
> com.gemstone.gemfire.internal.cache.persistence.PersistentReplicatedTestBase._createPersistentRegion(PersistentReplicatedTestBase.java:179)
> at
> com.gemstone.gemfire.internal.cache.persistence.PersistentReplicatedTestBase.createPersistentRegion(PersistentReplicatedTestBase.java:172)
> at
> com.gemstone.gemfire.internal.cache.persistence.PersistentRecoveryOrderDUnitTest.testCrashDuringPreparePersistentId(PersistentRecoveryOrderDUnitTest.java:1344)
> 7429 tests completed, 1 failed, 587 skipped
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (GEODE-1703) CI failure: PersistentRecoveryOrderDUnitTest.testCrashDuringPreparePersistentId fails assertion: Region not created within30000
[
https://issues.apache.org/jira/browse/GEODE-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395956#comment-15395956
]
ASF subversion and git services commented on GEODE-1703:
Commit 45830e3e15857bbe02daa6869ec07d8d1526ea4f in incubator-geode's branch
refs/heads/feature/GEODE-1385 from [~apa...@the9muses.net]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=45830e3 ]
GEODE-1703: add FlakyTest category to testCrashDuringPreparePersistentId
> CI failure:
> PersistentRecoveryOrderDUnitTest.testCrashDuringPreparePersistentId fails
> assertion: Region not created within3
> ---
>
> Key: GEODE-1703
> URL: https://issues.apache.org/jira/browse/GEODE-1703
> Project: Geode
> Issue Type: Bug
> Components: regions, tests
>Reporter: Kirk Lund
> Labels: flaky
>
> {noformat}
> :geode-core:distributedTest
> com.gemstone.gemfire.internal.cache.persistence.PersistentRecoveryOrderDUnitTest
> > testCrashDuringPreparePersistentId FAILED
> java.lang.AssertionError: Region not created within3
> at org.junit.Assert.fail(Assert.java:88)
> at
> com.gemstone.gemfire.internal.cache.persistence.PersistentReplicatedTestBase._createPersistentRegion(PersistentReplicatedTestBase.java:179)
> at
> com.gemstone.gemfire.internal.cache.persistence.PersistentReplicatedTestBase.createPersistentRegion(PersistentReplicatedTestBase.java:172)
> at
> com.gemstone.gemfire.internal.cache.persistence.PersistentRecoveryOrderDUnitTest.testCrashDuringPreparePersistentId(PersistentRecoveryOrderDUnitTest.java:1344)
> 7429 tests completed, 1 failed, 587 skipped
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (GEODE-1703) CI failure: PersistentRecoveryOrderDUnitTest.testCrashDuringPreparePersistentId fails assertion: Region not created within30000
Kirk Lund created GEODE-1703:
Summary: CI failure:
PersistentRecoveryOrderDUnitTest.testCrashDuringPreparePersistentId fails
assertion: Region not created within3
Key: GEODE-1703
URL: https://issues.apache.org/jira/browse/GEODE-1703
Project: Geode
Issue Type: Bug
Components: tests
Reporter: Kirk Lund
{noformat}
:geode-core:distributedTest
com.gemstone.gemfire.internal.cache.persistence.PersistentRecoveryOrderDUnitTest
> testCrashDuringPreparePersistentId FAILED
java.lang.AssertionError: Region not created within3
at org.junit.Assert.fail(Assert.java:88)
at
com.gemstone.gemfire.internal.cache.persistence.PersistentReplicatedTestBase._createPersistentRegion(PersistentReplicatedTestBase.java:179)
at
com.gemstone.gemfire.internal.cache.persistence.PersistentReplicatedTestBase.createPersistentRegion(PersistentReplicatedTestBase.java:172)
at
com.gemstone.gemfire.internal.cache.persistence.PersistentRecoveryOrderDUnitTest.testCrashDuringPreparePersistentId(PersistentRecoveryOrderDUnitTest.java:1344)
7429 tests completed, 1 failed, 587 skipped
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-1703) CI failure: PersistentRecoveryOrderDUnitTest.testCrashDuringPreparePersistentId fails assertion: Region not created within30000
[
https://issues.apache.org/jira/browse/GEODE-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-1703:
-
Component/s: regions
> CI failure:
> PersistentRecoveryOrderDUnitTest.testCrashDuringPreparePersistentId fails
> assertion: Region not created within3
> ---
>
> Key: GEODE-1703
> URL: https://issues.apache.org/jira/browse/GEODE-1703
> Project: Geode
> Issue Type: Bug
> Components: regions, tests
>Reporter: Kirk Lund
> Labels: flaky
>
> {noformat}
> :geode-core:distributedTest
> com.gemstone.gemfire.internal.cache.persistence.PersistentRecoveryOrderDUnitTest
> > testCrashDuringPreparePersistentId FAILED
> java.lang.AssertionError: Region not created within3
> at org.junit.Assert.fail(Assert.java:88)
> at
> com.gemstone.gemfire.internal.cache.persistence.PersistentReplicatedTestBase._createPersistentRegion(PersistentReplicatedTestBase.java:179)
> at
> com.gemstone.gemfire.internal.cache.persistence.PersistentReplicatedTestBase.createPersistentRegion(PersistentReplicatedTestBase.java:172)
> at
> com.gemstone.gemfire.internal.cache.persistence.PersistentRecoveryOrderDUnitTest.testCrashDuringPreparePersistentId(PersistentRecoveryOrderDUnitTest.java:1344)
> 7429 tests completed, 1 failed, 587 skipped
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (GEODE-1674) Race condition in HashIndexSetIterator leads to ArrayOutOfBoundsException
[ https://issues.apache.org/jira/browse/GEODE-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395976#comment-15395976 ] ASF subversion and git services commented on GEODE-1674: Commit 6e8f42f38af3914cea943a48c14f868590b8964e in incubator-geode's branch refs/heads/develop from [~nnag] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=6e8f42f ] GEODE-1674: Using a immuatable object to pass the HashIndexSet and its mask * Immutable ojects pairs the mask and set together * There is no race condition in which the mask differs from the set leading to any ArrayOutOfBoundsException. > Race condition in HashIndexSetIterator leads to ArrayOutOfBoundsException > - > > Key: GEODE-1674 > URL: https://issues.apache.org/jira/browse/GEODE-1674 > Project: Geode > Issue Type: Bug > Components: querying >Reporter: nabarun > > Object array may be reassigned by the time the function is trying to access > current element and the mask value may be larger than the size of the array > and this will lead to array out bounds exception. > location : private HashIndexSetIterator(Object keyToMatch, Object[] objects) > in HashIndexSet.java -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-1704) FixedPartitioningDUnitTest.testPut_ValidateDataOnMember_PrimarySecondary_Datastore
Kevin Duling created GEODE-1704:
---
Summary:
FixedPartitioningDUnitTest.testPut_ValidateDataOnMember_PrimarySecondary_Datastore
Key: GEODE-1704
URL: https://issues.apache.org/jira/browse/GEODE-1704
Project: Geode
Issue Type: Bug
Reporter: Kevin Duling
In Geode_develop_DistributedTests/3414:
{noformat}
Error Message
com.gemstone.gemfire.test.dunit.RMIException: While invoking
com.gemstone.gemfire.internal.cache.partitioned.fixed.FixedPartitioningDUnitTest$$Lambda$132/528994226.run
in VM 3 running on Host japan.gemstone.com with 4 VMs
Stacktrace
com.gemstone.gemfire.test.dunit.RMIException: While invoking
com.gemstone.gemfire.internal.cache.partitioned.fixed.FixedPartitioningDUnitTest$$Lambda$132/528994226.run
in VM 3 running on Host japan.gemstone.com with 4 VMs
at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:389)
at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:355)
at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:293)
at
com.gemstone.gemfire.internal.cache.partitioned.fixed.FixedPartitioningDUnitTest.testPut_ValidateDataOnMember_PrimarySecondary_Datastore(FixedPartitioningDUnitTest.java:1029)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
at
org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at
org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
at
org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
at
org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at
org.gradle.messaging.dispatch.ReflectionDispatch.dis
[jira] [Resolved] (GEODE-1674) Race condition in HashIndexSetIterator leads to ArrayOutOfBoundsException
[ https://issues.apache.org/jira/browse/GEODE-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nabarun resolved GEODE-1674. Resolution: Fixed > Race condition in HashIndexSetIterator leads to ArrayOutOfBoundsException > - > > Key: GEODE-1674 > URL: https://issues.apache.org/jira/browse/GEODE-1674 > Project: Geode > Issue Type: Bug > Components: querying >Reporter: nabarun > > Object array may be reassigned by the time the function is trying to access > current element and the mask value may be larger than the size of the array > and this will lead to array out bounds exception. > location : private HashIndexSetIterator(Object keyToMatch, Object[] objects) > in HashIndexSet.java -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1703) CI failure: PersistentRecoveryOrderDUnitTest.testCrashDuringPreparePersistentId fails assertion: Region not created within30000
[
https://issues.apache.org/jira/browse/GEODE-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395978#comment-15395978
]
ASF subversion and git services commented on GEODE-1703:
Commit 19361b6b264107ee322cd4e8fff2fc69c38cbdf5 in incubator-geode's branch
refs/heads/develop from [~apa...@the9muses.net]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=19361b6 ]
GEODE-1703: add FlakyTest category to testCrashDuringPreparePersistentId
> CI failure:
> PersistentRecoveryOrderDUnitTest.testCrashDuringPreparePersistentId fails
> assertion: Region not created within3
> ---
>
> Key: GEODE-1703
> URL: https://issues.apache.org/jira/browse/GEODE-1703
> Project: Geode
> Issue Type: Bug
> Components: regions, tests
>Reporter: Kirk Lund
> Labels: flaky
>
> {noformat}
> :geode-core:distributedTest
> com.gemstone.gemfire.internal.cache.persistence.PersistentRecoveryOrderDUnitTest
> > testCrashDuringPreparePersistentId FAILED
> java.lang.AssertionError: Region not created within3
> at org.junit.Assert.fail(Assert.java:88)
> at
> com.gemstone.gemfire.internal.cache.persistence.PersistentReplicatedTestBase._createPersistentRegion(PersistentReplicatedTestBase.java:179)
> at
> com.gemstone.gemfire.internal.cache.persistence.PersistentReplicatedTestBase.createPersistentRegion(PersistentReplicatedTestBase.java:172)
> at
> com.gemstone.gemfire.internal.cache.persistence.PersistentRecoveryOrderDUnitTest.testCrashDuringPreparePersistentId(PersistentRecoveryOrderDUnitTest.java:1344)
> 7429 tests completed, 1 failed, 587 skipped
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (GEODE-1385) CI Failure: MiscellaneousCommandsDUnitTest.testShutDownForTIMEOUT
[
https://issues.apache.org/jira/browse/GEODE-1385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395977#comment-15395977
]
ASF subversion and git services commented on GEODE-1385:
Commit 96f1d7a3272d7e60f4e28e4ef02f7a7f862af8a1 in incubator-geode's branch
refs/heads/develop from [~apa...@the9muses.net]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=96f1d7a ]
GEODE-1385: add FlakyTest category to testShutDownForTIMEOUT
> CI Failure: MiscellaneousCommandsDUnitTest.testShutDownForTIMEOUT
> -
>
> Key: GEODE-1385
> URL: https://issues.apache.org/jira/browse/GEODE-1385
> Project: Geode
> Issue Type: Bug
> Components: management
>Reporter: Barry Oglesby
>Assignee: Kirk Lund
> Labels: ci
>
> Geode_develop_DistributedTests
> Private Build #2546 (May 10, 2016 7:09:11 AM)
> Revision: 44c2f398ff0a67d3e639c224c7df3ec861fe2c70
> Error Message
> {noformat}
> com.gemstone.gemfire.test.dunit.RMIException: While invoking
> com.gemstone.gemfire.test.dunit.NamedCallable.call in VM 0 running on Host
> buildtest.gemstone.com with 4 VMs
> {noformat}
> Stacktrace
> {noformat}
> com.gemstone.gemfire.test.dunit.RMIException: While invoking
> com.gemstone.gemfire.test.dunit.NamedCallable.call in VM 0 running on Host
> buildtest.gemstone.com with 4 VMs
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:389)
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:355)
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:308)
> at
> com.gemstone.gemfire.management.internal.cli.commands.CliCommandTestBase.setUpJMXManagerOnVM(CliCommandTestBase.java:117)
> at
> com.gemstone.gemfire.management.internal.cli.commands.CliCommandTestBase.setUpJmxManagerOnVm0ThenConnect(CliCommandTestBase.java:111)
> at
> com.gemstone.gemfire.management.internal.cli.commands.MiscellaneousCommandsDUnitTest.setupForShutDown(MiscellaneousCommandsDUnitTest.java:357)
> at
> com.gemstone.gemfire.management.internal.cli.commands.MiscellaneousCommandsDUnitTest.testShutDownForTIMEOUT(MiscellaneousCommandsDUnitTest.java:306)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
> at sun.reflect.GeneratedMethodAccessor335.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
>
[jira] [Issue Comment Deleted] (GEODE-1385) CI Failure: MiscellaneousCommandsDUnitTest.testShutDownForTIMEOUT
[
https://issues.apache.org/jira/browse/GEODE-1385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-1385:
-
Comment: was deleted
(was: Commit f734610ade3b21ee961344287281b582711bfa00 in incubator-geode's
branch refs/heads/feature/GEODE-1385 from [~apa...@the9muses.net]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=f734610 ]
GEODE-1385: mark testShutDownForTIMEOUT with FlakyTest category
)
> CI Failure: MiscellaneousCommandsDUnitTest.testShutDownForTIMEOUT
> -
>
> Key: GEODE-1385
> URL: https://issues.apache.org/jira/browse/GEODE-1385
> Project: Geode
> Issue Type: Bug
> Components: management
>Reporter: Barry Oglesby
>Assignee: Kirk Lund
> Labels: ci
>
> Geode_develop_DistributedTests
> Private Build #2546 (May 10, 2016 7:09:11 AM)
> Revision: 44c2f398ff0a67d3e639c224c7df3ec861fe2c70
> Error Message
> {noformat}
> com.gemstone.gemfire.test.dunit.RMIException: While invoking
> com.gemstone.gemfire.test.dunit.NamedCallable.call in VM 0 running on Host
> buildtest.gemstone.com with 4 VMs
> {noformat}
> Stacktrace
> {noformat}
> com.gemstone.gemfire.test.dunit.RMIException: While invoking
> com.gemstone.gemfire.test.dunit.NamedCallable.call in VM 0 running on Host
> buildtest.gemstone.com with 4 VMs
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:389)
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:355)
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:308)
> at
> com.gemstone.gemfire.management.internal.cli.commands.CliCommandTestBase.setUpJMXManagerOnVM(CliCommandTestBase.java:117)
> at
> com.gemstone.gemfire.management.internal.cli.commands.CliCommandTestBase.setUpJmxManagerOnVm0ThenConnect(CliCommandTestBase.java:111)
> at
> com.gemstone.gemfire.management.internal.cli.commands.MiscellaneousCommandsDUnitTest.setupForShutDown(MiscellaneousCommandsDUnitTest.java:357)
> at
> com.gemstone.gemfire.management.internal.cli.commands.MiscellaneousCommandsDUnitTest.testShutDownForTIMEOUT(MiscellaneousCommandsDUnitTest.java:306)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
> at sun.reflect.GeneratedMethodAccessor335.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDisp
[jira] [Created] (GEODE-1705) DurableClientCommandsDUnitTest.testCloseDurableCQ
Kevin Duling created GEODE-1705:
---
Summary: DurableClientCommandsDUnitTest.testCloseDurableCQ
Key: GEODE-1705
URL: https://issues.apache.org/jira/browse/GEODE-1705
Project: Geode
Issue Type: Bug
Reporter: Kevin Duling
In Geode_develop_DistributedTests/3414:
{noformat}
Error Message
java.lang.AssertionError
Stacktrace
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertTrue(Assert.java:52)
at
com.gemstone.gemfire.management.internal.cli.commands.DurableClientCommandsDUnitTest.testCloseDurableCQ(DurableClientCommandsDUnitTest.java:138)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
at
org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
at sun.reflect.GeneratedMethodAccessor377.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at
org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
at
org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
at
org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
at sun.reflect.GeneratedMethodAccessor376.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at
org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
at
org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
at
org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolEx
[jira] [Issue Comment Deleted] (GEODE-1703) CI failure: PersistentRecoveryOrderDUnitTest.testCrashDuringPreparePersistentId fails assertion: Region not created within30000
[
https://issues.apache.org/jira/browse/GEODE-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-1703:
-
Comment: was deleted
(was: Commit 45830e3e15857bbe02daa6869ec07d8d1526ea4f in incubator-geode's
branch refs/heads/feature/GEODE-1385 from [~apa...@the9muses.net]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=45830e3 ]
GEODE-1703: add FlakyTest category to testCrashDuringPreparePersistentId
)
> CI failure:
> PersistentRecoveryOrderDUnitTest.testCrashDuringPreparePersistentId fails
> assertion: Region not created within3
> ---
>
> Key: GEODE-1703
> URL: https://issues.apache.org/jira/browse/GEODE-1703
> Project: Geode
> Issue Type: Bug
> Components: regions, tests
>Reporter: Kirk Lund
> Labels: flaky
>
> {noformat}
> :geode-core:distributedTest
> com.gemstone.gemfire.internal.cache.persistence.PersistentRecoveryOrderDUnitTest
> > testCrashDuringPreparePersistentId FAILED
> java.lang.AssertionError: Region not created within3
> at org.junit.Assert.fail(Assert.java:88)
> at
> com.gemstone.gemfire.internal.cache.persistence.PersistentReplicatedTestBase._createPersistentRegion(PersistentReplicatedTestBase.java:179)
> at
> com.gemstone.gemfire.internal.cache.persistence.PersistentReplicatedTestBase.createPersistentRegion(PersistentReplicatedTestBase.java:172)
> at
> com.gemstone.gemfire.internal.cache.persistence.PersistentRecoveryOrderDUnitTest.testCrashDuringPreparePersistentId(PersistentRecoveryOrderDUnitTest.java:1344)
> 7429 tests completed, 1 failed, 587 skipped
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (GEODE-1706) miscellaneouscommandsdunittest.testshutdownwithouttime...@com.gemstone.gemfire.management.internal.cli.commands.CommandOverHttpDUnitTest
Kevin Duling created GEODE-1706:
---
Summary:
miscellaneouscommandsdunittest.testshutdownwithouttime...@com.gemstone.gemfire.management.internal.cli.commands.CommandOverHttpDUnitTest
Key: GEODE-1706
URL: https://issues.apache.org/jira/browse/GEODE-1706
Project: Geode
Issue Type: Bug
Reporter: Kevin Duling
In Geode_develop_DistributedTests/3411:
{noformat}
Error Message
java.lang.AssertionError: Event never occurred after 1000 ms: Waits for the
shell to disconnect!
Stacktrace
java.lang.AssertionError: Event never occurred after 1000 ms: Waits for the
shell to disconnect!
at org.junit.Assert.fail(Assert.java:88)
at com.gemstone.gemfire.test.dunit.Wait.waitForCriterion(Wait.java:185)
at
com.gemstone.gemfire.management.internal.cli.commands.MiscellaneousCommandsDUnitTest.testShutDownWithoutTimeout(MiscellaneousCommandsDUnitTest.java:245)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.junit.runners.Suite.runChild(Suite.java:128)
at org.junit.runners.Suite.runChild(Suite.java:27)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
at
org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at
org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at
org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
at
org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
[jira] [Updated] (GEODE-1385) CI Failure: MiscellaneousCommandsDUnitTest.testShutDownForTIMEOUT
[
https://issues.apache.org/jira/browse/GEODE-1385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-1385:
-
Labels: ci flaky (was: ci)
> CI Failure: MiscellaneousCommandsDUnitTest.testShutDownForTIMEOUT
> -
>
> Key: GEODE-1385
> URL: https://issues.apache.org/jira/browse/GEODE-1385
> Project: Geode
> Issue Type: Bug
> Components: management
>Reporter: Barry Oglesby
>Assignee: Kirk Lund
> Labels: ci, flaky
>
> Geode_develop_DistributedTests
> Private Build #2546 (May 10, 2016 7:09:11 AM)
> Revision: 44c2f398ff0a67d3e639c224c7df3ec861fe2c70
> Error Message
> {noformat}
> com.gemstone.gemfire.test.dunit.RMIException: While invoking
> com.gemstone.gemfire.test.dunit.NamedCallable.call in VM 0 running on Host
> buildtest.gemstone.com with 4 VMs
> {noformat}
> Stacktrace
> {noformat}
> com.gemstone.gemfire.test.dunit.RMIException: While invoking
> com.gemstone.gemfire.test.dunit.NamedCallable.call in VM 0 running on Host
> buildtest.gemstone.com with 4 VMs
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:389)
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:355)
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:308)
> at
> com.gemstone.gemfire.management.internal.cli.commands.CliCommandTestBase.setUpJMXManagerOnVM(CliCommandTestBase.java:117)
> at
> com.gemstone.gemfire.management.internal.cli.commands.CliCommandTestBase.setUpJmxManagerOnVm0ThenConnect(CliCommandTestBase.java:111)
> at
> com.gemstone.gemfire.management.internal.cli.commands.MiscellaneousCommandsDUnitTest.setupForShutDown(MiscellaneousCommandsDUnitTest.java:357)
> at
> com.gemstone.gemfire.management.internal.cli.commands.MiscellaneousCommandsDUnitTest.testShutDownForTIMEOUT(MiscellaneousCommandsDUnitTest.java:306)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
> at sun.reflect.GeneratedMethodAccessor335.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
>
[jira] [Commented] (GEODE-93) Entry count stats are incorrect with PR with entry eviction and async disk
[ https://issues.apache.org/jira/browse/GEODE-93?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15396030#comment-15396030 ] ASF subversion and git services commented on GEODE-93: -- Commit 9389c6fece1adb3e83bc7a8863a2d84f52bfc0fa in incubator-geode's branch refs/heads/develop from [~dschneider] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=9389c6f ] GEODE-1700: fix stat corrupting when async queue full A common method is now used for writing async ops to disk. The same method is now used for both flushing an item that has been taken out of the queue and for when the queue is full causing a sync write to be done. Also did a minor refactoring to get rid of the "removed" flag. This revision fixes a bug introduced in GEODE-93 and should be included with that fix. > Entry count stats are incorrect with PR with entry eviction and async disk > -- > > Key: GEODE-93 > URL: https://issues.apache.org/jira/browse/GEODE-93 > Project: Geode > Issue Type: Bug > Components: eviction >Reporter: Dan Smith >Assignee: Sai Boorlagadda > Fix For: 1.0.0-incubating.M3 > > Attachments: > 0001-Test-that-demonstrates-incorrect-entriesOnDisk-and-e.patch > > > I discovered this while writing a unit test for GEODE-56. It looks like when > doing operations on a PR with entry eviction of 1, overflow to disk, and > asynchronous persistence, the stats fo entries in memory and entries on disk > are incorrect. Entries in memory is too high and entriesOnDisk goes negative. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1700) The DiskRegionStats entriesInVM and entriesOnlyOnDisk for overflow lru regions with async disk may be wrong
[ https://issues.apache.org/jira/browse/GEODE-1700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15396029#comment-15396029 ] ASF subversion and git services commented on GEODE-1700: Commit 9389c6fece1adb3e83bc7a8863a2d84f52bfc0fa in incubator-geode's branch refs/heads/develop from [~dschneider] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=9389c6f ] GEODE-1700: fix stat corrupting when async queue full A common method is now used for writing async ops to disk. The same method is now used for both flushing an item that has been taken out of the queue and for when the queue is full causing a sync write to be done. Also did a minor refactoring to get rid of the "removed" flag. This revision fixes a bug introduced in GEODE-93 and should be included with that fix. > The DiskRegionStats entriesInVM and entriesOnlyOnDisk for overflow lru > regions with async disk may be wrong > --- > > Key: GEODE-1700 > URL: https://issues.apache.org/jira/browse/GEODE-1700 > Project: Geode > Issue Type: Bug > Components: persistence >Reporter: Darrel Schneider >Assignee: Darrel Schneider > > The DiskRegionStats entriesInVM and entriesOnlyOnDisk for overflow lru > regions with async disk may be wrong. > A race condition exists that can cause the async queue to fill. In that case > additional evictions are written to disk immediately instead of going into > the queue. The code for this condition (handleFullAsyncQueue) was not updated > when a recent change was made to how the stats entriesInVM and > entriesOnlyOnDisk were updated. > This can also cause partition balancing decisions to be wrong since this size > of the bucket can be larger than it should be. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-1700) The DiskRegionStats entriesInVM and entriesOnlyOnDisk for overflow lru regions with async disk may be wrong
[ https://issues.apache.org/jira/browse/GEODE-1700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider resolved GEODE-1700. - Resolution: Fixed Fix Version/s: 1.0.0-incubating > The DiskRegionStats entriesInVM and entriesOnlyOnDisk for overflow lru > regions with async disk may be wrong > --- > > Key: GEODE-1700 > URL: https://issues.apache.org/jira/browse/GEODE-1700 > Project: Geode > Issue Type: Bug > Components: persistence >Reporter: Darrel Schneider >Assignee: Darrel Schneider > Fix For: 1.0.0-incubating > > > The DiskRegionStats entriesInVM and entriesOnlyOnDisk for overflow lru > regions with async disk may be wrong. > A race condition exists that can cause the async queue to fill. In that case > additional evictions are written to disk immediately instead of going into > the queue. The code for this condition (handleFullAsyncQueue) was not updated > when a recent change was made to how the stats entriesInVM and > entriesOnlyOnDisk were updated. > This can also cause partition balancing decisions to be wrong since this size > of the bucket can be larger than it should be. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-64) configure Sonar plugin as part of the Gradle build
[ https://issues.apache.org/jira/browse/GEODE-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15396088#comment-15396088 ] ASF subversion and git services commented on GEODE-64: -- Commit cb1b2f0be382e3ca03db1d951666f4d15cba43d3 in incubator-geode's branch refs/heads/feature/GEODE-64 from [~mbretl] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=cb1b2f0 ] GEODE-64: Add SonarQube Plugin And Initial Configuration Adding SonarQube plugin with basic configuration and can be integrated with the SonarQube Scanner. Configuration was tested on a local installation to verify scan completes, however, it will need to change once on Apache infrastructure > configure Sonar plugin as part of the Gradle build > -- > > Key: GEODE-64 > URL: https://issues.apache.org/jira/browse/GEODE-64 > Project: Geode > Issue Type: Improvement > Components: build >Affects Versions: 1.0.0-incubating >Reporter: Roman Shaposhnik >Assignee: Mark Bretl > > Seems like we need to configure Sonar on our end before we can take advantage > of what INFRA has setup for us as part of INFRA-9616 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1675) Session Management modules need to be updated to work with Tomcat 8.5
[ https://issues.apache.org/jira/browse/GEODE-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15396121#comment-15396121 ] ASF subversion and git services commented on GEODE-1675: Commit a6e9569f510eb3bda736474e508b7832e63453ec in incubator-geode's branch refs/heads/develop from [~huynhja] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=a6e9569 ] GEODE-1675: Session Management modules need to be updated to work with Tomcat 8.5.4 * Extracted DeltaSessionInterface to allow shared code between classes for Tomcat 6,7,8 * Added new test classes > Session Management modules need to be updated to work with Tomcat 8.5 > - > > Key: GEODE-1675 > URL: https://issues.apache.org/jira/browse/GEODE-1675 > Project: Geode > Issue Type: New Feature > Components: http session >Reporter: Jason Huynh >Assignee: Jason Huynh > > Update support for Tomcat 8.5. There are various api changes that need to be > used and others that have been removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1666) Parallelize Gradle test execution
[ https://issues.apache.org/jira/browse/GEODE-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15396263#comment-15396263 ] ASF subversion and git services commented on GEODE-1666: Commit 97a8452e7f092dae68af8fa8eb51df3b333b2820 in incubator-geode's branch refs/heads/feature/GEODE-1666 from [~jens.deppe] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=97a8452 ] GEODE-1666: Move docker config to closed side > Parallelize Gradle test execution > - > > Key: GEODE-1666 > URL: https://issues.apache.org/jira/browse/GEODE-1666 > Project: Geode > Issue Type: Improvement > Components: build >Reporter: Jens Deppe > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1666) Parallelize Gradle test execution
[ https://issues.apache.org/jira/browse/GEODE-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15396355#comment-15396355 ] ASF subversion and git services commented on GEODE-1666: Commit ad2d8886527003855b78585bb2aed1dc08617613 in incubator-geode's branch refs/heads/feature/GEODE-1666 from [~jens.deppe] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=ad2d888 ] GEODE-1666: Remove lingering docker plugin setup > Parallelize Gradle test execution > - > > Key: GEODE-1666 > URL: https://issues.apache.org/jira/browse/GEODE-1666 > Project: Geode > Issue Type: Improvement > Components: build >Reporter: Jens Deppe > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-11) Lucene Integration
[ https://issues.apache.org/jira/browse/GEODE-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15396400#comment-15396400 ] ASF GitHub Bot commented on GEODE-11: - Github user gesterzhou commented on the issue: https://github.com/apache/incubator-geode/pull/217 +1 > Lucene Integration > -- > > Key: GEODE-11 > URL: https://issues.apache.org/jira/browse/GEODE-11 > Project: Geode > Issue Type: New Feature > Components: querying >Reporter: Dan Smith >Assignee: xiaojian zhou > > This is a feature that has been under development for GemFire but was not > part of the initial drop of code for geode. > Allow Lucene indexes to be stored in Geode regions allowing users to do text > searches on data stored in Geode. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-11) Lucene Integration
[ https://issues.apache.org/jira/browse/GEODE-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15396433#comment-15396433 ] ASF GitHub Bot commented on GEODE-11: - Github user asfgit closed the pull request at: https://github.com/apache/incubator-geode/pull/217 > Lucene Integration > -- > > Key: GEODE-11 > URL: https://issues.apache.org/jira/browse/GEODE-11 > Project: Geode > Issue Type: New Feature > Components: querying >Reporter: Dan Smith >Assignee: xiaojian zhou > > This is a feature that has been under development for GemFire but was not > part of the initial drop of code for geode. > Allow Lucene indexes to be stored in Geode regions allowing users to do text > searches on data stored in Geode. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-11) Lucene Integration
[ https://issues.apache.org/jira/browse/GEODE-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15396429#comment-15396429 ] ASF subversion and git services commented on GEODE-11: -- Commit de3f90e03472818079e6a0892c6ff3d221298c8e in incubator-geode's branch refs/heads/develop from [~adharmakkan] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=de3f90e ] GEODE-11: defined index will be saved and can be found. This closes #217 GEODE-11: Adding a defined index field in LuceneServiceImpl Added a definedIndexMap field in LuceneServiceImpl to store the uninitialized lucene indexes Signed-off-by: Gester Zhou GEODE-11: Added status to gfsh commands Added a field status(initialized/defined wrt region creation) to list and describe lucene commands. Added a dunit test for create index command to verify that the created index is stored in definedIndexMap. Signed-off-by: Gester Zhou GEODE-11: Removed methods from LuceneService interface Removed methods accessing definedIndexMap from the LuceneServiceInterface. Made few other method and field name changes as per review comments. > Lucene Integration > -- > > Key: GEODE-11 > URL: https://issues.apache.org/jira/browse/GEODE-11 > Project: Geode > Issue Type: New Feature > Components: querying >Reporter: Dan Smith >Assignee: xiaojian zhou > > This is a feature that has been under development for GemFire but was not > part of the initial drop of code for geode. > Allow Lucene indexes to be stored in Geode regions allowing users to do text > searches on data stored in Geode. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-11) Lucene Integration
[ https://issues.apache.org/jira/browse/GEODE-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15396431#comment-15396431 ] ASF subversion and git services commented on GEODE-11: -- Commit de3f90e03472818079e6a0892c6ff3d221298c8e in incubator-geode's branch refs/heads/develop from [~adharmakkan] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=de3f90e ] GEODE-11: defined index will be saved and can be found. This closes #217 GEODE-11: Adding a defined index field in LuceneServiceImpl Added a definedIndexMap field in LuceneServiceImpl to store the uninitialized lucene indexes Signed-off-by: Gester Zhou GEODE-11: Added status to gfsh commands Added a field status(initialized/defined wrt region creation) to list and describe lucene commands. Added a dunit test for create index command to verify that the created index is stored in definedIndexMap. Signed-off-by: Gester Zhou GEODE-11: Removed methods from LuceneService interface Removed methods accessing definedIndexMap from the LuceneServiceInterface. Made few other method and field name changes as per review comments. > Lucene Integration > -- > > Key: GEODE-11 > URL: https://issues.apache.org/jira/browse/GEODE-11 > Project: Geode > Issue Type: New Feature > Components: querying >Reporter: Dan Smith >Assignee: xiaojian zhou > > This is a feature that has been under development for GemFire but was not > part of the initial drop of code for geode. > Allow Lucene indexes to be stored in Geode regions allowing users to do text > searches on data stored in Geode. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-11) Lucene Integration
[ https://issues.apache.org/jira/browse/GEODE-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15396432#comment-15396432 ] ASF subversion and git services commented on GEODE-11: -- Commit de3f90e03472818079e6a0892c6ff3d221298c8e in incubator-geode's branch refs/heads/develop from [~adharmakkan] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=de3f90e ] GEODE-11: defined index will be saved and can be found. This closes #217 GEODE-11: Adding a defined index field in LuceneServiceImpl Added a definedIndexMap field in LuceneServiceImpl to store the uninitialized lucene indexes Signed-off-by: Gester Zhou GEODE-11: Added status to gfsh commands Added a field status(initialized/defined wrt region creation) to list and describe lucene commands. Added a dunit test for create index command to verify that the created index is stored in definedIndexMap. Signed-off-by: Gester Zhou GEODE-11: Removed methods from LuceneService interface Removed methods accessing definedIndexMap from the LuceneServiceInterface. Made few other method and field name changes as per review comments. > Lucene Integration > -- > > Key: GEODE-11 > URL: https://issues.apache.org/jira/browse/GEODE-11 > Project: Geode > Issue Type: New Feature > Components: querying >Reporter: Dan Smith >Assignee: xiaojian zhou > > This is a feature that has been under development for GemFire but was not > part of the initial drop of code for geode. > Allow Lucene indexes to be stored in Geode regions allowing users to do text > searches on data stored in Geode. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-11) Lucene Integration
[ https://issues.apache.org/jira/browse/GEODE-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15396430#comment-15396430 ] ASF subversion and git services commented on GEODE-11: -- Commit de3f90e03472818079e6a0892c6ff3d221298c8e in incubator-geode's branch refs/heads/develop from [~adharmakkan] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=de3f90e ] GEODE-11: defined index will be saved and can be found. This closes #217 GEODE-11: Adding a defined index field in LuceneServiceImpl Added a definedIndexMap field in LuceneServiceImpl to store the uninitialized lucene indexes Signed-off-by: Gester Zhou GEODE-11: Added status to gfsh commands Added a field status(initialized/defined wrt region creation) to list and describe lucene commands. Added a dunit test for create index command to verify that the created index is stored in definedIndexMap. Signed-off-by: Gester Zhou GEODE-11: Removed methods from LuceneService interface Removed methods accessing definedIndexMap from the LuceneServiceInterface. Made few other method and field name changes as per review comments. > Lucene Integration > -- > > Key: GEODE-11 > URL: https://issues.apache.org/jira/browse/GEODE-11 > Project: Geode > Issue Type: New Feature > Components: querying >Reporter: Dan Smith >Assignee: xiaojian zhou > > This is a feature that has been under development for GemFire but was not > part of the initial drop of code for geode. > Allow Lucene indexes to be stored in Geode regions allowing users to do text > searches on data stored in Geode. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1701) GeodePermission does not need Geode in the class name
[ https://issues.apache.org/jira/browse/GEODE-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15396475#comment-15396475 ] ASF subversion and git services commented on GEODE-1701: Commit 990f552b47dec3232b68aad2a463b801632d97c1 in incubator-geode's branch refs/heads/feature/GEODE-1701 from [~apa...@the9muses.net] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=990f552 ] GEODE-1701: rename GeodePermission as ResourcePermission > GeodePermission does not need Geode in the class name > - > > Key: GEODE-1701 > URL: https://issues.apache.org/jira/browse/GEODE-1701 > Project: Geode > Issue Type: Sub-task > Components: security >Reporter: Kirk Lund >Assignee: Kirk Lund > > Remove product name "Geode" from GeodePermission. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-420) locator ssl configuration
[ https://issues.apache.org/jira/browse/GEODE-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15396573#comment-15396573 ] ASF subversion and git services commented on GEODE-420: --- Commit 115e5f25dc4138f90c29452ad8eea987215e2261 in incubator-geode's branch refs/heads/feature/GEODE-420 from [~bschuchardt] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=115e5f2 ] GEODE-420 Changing TcpClient to not be a static class TcpClient now holds the SocketCreator that it should use to connect to locators. It's currently using the cluster SocketCreator but will be changed to use the one for the Locator component when it's available. > locator ssl configuration > - > > Key: GEODE-420 > URL: https://issues.apache.org/jira/browse/GEODE-420 > Project: Geode > Issue Type: New Feature > Components: locator >Reporter: Darrel Schneider >Assignee: Udo Kohlmeyer > > We currently allow separate SSL configuration for cluster, server, gateway, > jmx-manager, and http-service. > The "server" attributes configure the ssl connections from clients to a cache > server. > The "gateway" attributes configure the ssl connections between a gateway > sender and receiver. > The "jmx-manager" attributes configure the ssl connections between an admin > client (for example gfsh) and the jmx-manager. > The "http-service" attributes configure the ssl connections between REST > clients and the http-service. > The "cluster" attributes configure the ssl connections between the members of > a distributed system (peer-to-peer connections) AND to the locators. > Using "cluster" for the connections to a locator can be a problem. > Say you trust all your members of a distributed system since they are running > on your private network. So no need for ssl on the p2p connections. > So you disable cluster-ssl. These means that your peers are locators are all > using unsecure connections. > But some of these members are hosting a cache server and have clients > connecting to them. So you configure "server" ssl for the client to server > connections. But for your clients to find you servers they need to talk to > the locator. Since the clients are coming from the outside world you want > them to use SSL. So you configure "server" ssl on them for when they connect > to the cache server and "cluster" SSL on them for when they connect to the > locator. But your locators are configured with "cluster" SSL disabled so that > the p2p connects on the internal network will not be SSL. > So you are either forced to have you client to locator connections to be > unsecure or you need to secure all the cluster connections forcing the peers > to also use SSL. > I think we should introduce "locator" SSL configuration options that would > allow you to have just the locator and server using SSL and the "cluster" to > have SSL disabled. > Something else to consider would be for the locator to be able to use SSL for > clients but non-SSL for locator-to-locator and peers-to-locator connections. > I think this would be more complicated because we would need to have > different ports that the locator listens on (one for clients and one for > locators and members). > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-11) Lucene Integration
[ https://issues.apache.org/jira/browse/GEODE-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15396631#comment-15396631 ] ASF GitHub Bot commented on GEODE-11: - GitHub user aparnard opened a pull request: https://github.com/apache/incubator-geode/pull/219 feature/GEODE-11-Lucene search with limit and pagination in gfsh - Added limit option to the lucene search gfsh command to limit the number of search results to return. - Added page size option to the lucene search gfsh command to paginate the search results. - Added dunit and junit tests to verify the above. You can merge this pull request into a Git repository by running: $ git pull https://github.com/aparnard/incubator-geode feature/GEODE-11-gfsh-lucene-query Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-geode/pull/219.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #219 commit 4285edd41910297e1d921059582692da85c28a67 Author: Aparna Dharmakkan Date: 2016-07-20T20:50:59Z GEODE-11: Added Limit to lucene search gfsh commands Added an option to specify limit in gfsh search. Added a dunit test to verify. commit 801bbe98751aa52111a07f492ec9ef08f97e85a2 Author: Aparna Dharmakkan Date: 2016-07-27T21:40:08Z GEODE-11 : Pagination for gfsh lucene search command Added pagination for gfsh lucene search results. Added junit test to verify. > Lucene Integration > -- > > Key: GEODE-11 > URL: https://issues.apache.org/jira/browse/GEODE-11 > Project: Geode > Issue Type: New Feature > Components: querying >Reporter: Dan Smith >Assignee: xiaojian zhou > > This is a feature that has been under development for GemFire but was not > part of the initial drop of code for geode. > Allow Lucene indexes to be stored in Geode regions allowing users to do text > searches on data stored in Geode. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-1707) Create missing package javadocs
Bruce Schuchardt created GEODE-1707: --- Summary: Create missing package javadocs Key: GEODE-1707 URL: https://issues.apache.org/jira/browse/GEODE-1707 Project: Geode Issue Type: Bug Components: general Reporter: Bruce Schuchardt When you bring up the Geode javadocs there are a lot of packages that are missing descriptions. When someone is looking over the packages they need to know what they contain. * com.gemstone.gemfire.cache.wan * com.gemstone.gemfire.compression * com.gemstone.gemfire.i18n * com.gemstone.gemfire.lang * com.gemstone.gemfire.management.membership * com.gemstone.gemfire.memcached * com.gemstone.gemfire.modules.gatewaydelta * com.gemstone.gemfire.modules.hibernate * com.gemstone.gemfire.modules.session.bootstrap * com.gemstone.gemfire.modules.session.catalina * com.gemstone.gemfire.modules.session.catalina.callback * com.gemstone.gemfire.modules.session.filter * com.gemstone.gemfire.modules.session.installer * com.gemstone.gemfire.modules.session.installer.args * com.gemstone.gemfire.modules.util * com.gemstone.gemfire.ra These directories must have a package.html that has, at a minimum, a paragraph describing the package. I can't even tell what the com.gemstone.gemfire.ra package is about after looking at the two items it contains. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1682) provide ability to start developer REST api from gfsh
[
https://issues.apache.org/jira/browse/GEODE-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15396660#comment-15396660
]
ASF GitHub Bot commented on GEODE-1682:
---
Github user sbawaska commented on the issue:
https://github.com/apache/incubator-geode/pull/218
+1
> provide ability to start developer REST api from gfsh
> -
>
> Key: GEODE-1682
> URL: https://issues.apache.org/jira/browse/GEODE-1682
> Project: Geode
> Issue Type: Sub-task
> Components: gfsh
>Reporter: Swapnil Bawaskar
>Assignee: Avinash
>
> To start REST api users have to add {{--J=-Dgemfire.start-dev-rest-api=true}}
> to the {{start server}} command.
> There should be a {noformat}--start-rest-api{noformat} option for the {{start
> server}} command to start the rest api a
> {noformat}--http-service-port{noformat} to configure the port and a
> {noformat}--http-service-bind-address{noformat} option for the bind address.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-1707) Create missing package javadocs
[ https://issues.apache.org/jira/browse/GEODE-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt updated GEODE-1707: Assignee: Anthony Baker > Create missing package javadocs > --- > > Key: GEODE-1707 > URL: https://issues.apache.org/jira/browse/GEODE-1707 > Project: Geode > Issue Type: Bug > Components: general >Reporter: Bruce Schuchardt >Assignee: Anthony Baker > > When you bring up the Geode javadocs there are a lot of packages that are > missing descriptions. When someone is looking over the packages they need to > know what they contain. > * com.gemstone.gemfire.cache.wan > * com.gemstone.gemfire.compression > * com.gemstone.gemfire.i18n > * com.gemstone.gemfire.lang > * com.gemstone.gemfire.management.membership > * com.gemstone.gemfire.memcached > * com.gemstone.gemfire.modules.gatewaydelta > * com.gemstone.gemfire.modules.hibernate > * com.gemstone.gemfire.modules.session.bootstrap > * com.gemstone.gemfire.modules.session.catalina > * com.gemstone.gemfire.modules.session.catalina.callback > * com.gemstone.gemfire.modules.session.filter > * com.gemstone.gemfire.modules.session.installer > * com.gemstone.gemfire.modules.session.installer.args > * com.gemstone.gemfire.modules.util > * com.gemstone.gemfire.ra > These directories must have a package.html that has, at a minimum, a > paragraph describing the package. I can't even tell what the > com.gemstone.gemfire.ra package is about after looking at the two items it > contains. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1682) provide ability to start developer REST api from gfsh
[
https://issues.apache.org/jira/browse/GEODE-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15396713#comment-15396713
]
ASF GitHub Bot commented on GEODE-1682:
---
Github user davinash commented on the issue:
https://github.com/apache/incubator-geode/pull/218
what is the next step for merge, I do not see that option. May be I am
missing something !!!
> provide ability to start developer REST api from gfsh
> -
>
> Key: GEODE-1682
> URL: https://issues.apache.org/jira/browse/GEODE-1682
> Project: Geode
> Issue Type: Sub-task
> Components: gfsh
>Reporter: Swapnil Bawaskar
>Assignee: Avinash
>
> To start REST api users have to add {{--J=-Dgemfire.start-dev-rest-api=true}}
> to the {{start server}} command.
> There should be a {noformat}--start-rest-api{noformat} option for the {{start
> server}} command to start the rest api a
> {noformat}--http-service-port{noformat} to configure the port and a
> {noformat}--http-service-bind-address{noformat} option for the bind address.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
