[jira] [Updated] (GEODE-5229) Server logs exception from Protobuf connections when closing
[
https://issues.apache.org/jira/browse/GEODE-5229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Galen O'Sullivan updated GEODE-5229:
Description:
I'm not sure whether this issue happens exclusively on shutdown, but it does
happen reliably on shutdown when a connection from a Protobuf client is open,
and the exception is logged per-connection, potentially leaving a lot in the
logs. This happens despite the fix to GEODE-4300.
{code}
[info 2018/05/17 17:03:11.748 PDT tid=1] Cache server on port 21,497 is
shutting down.
[info 2018/05/17 17:03:11.750 PDT
tid=51] Invalid message
org.apache.geode.internal.protocol.protobuf.v1.serializer.exception.InvalidProtocolMessageException:
Failed to parse Protobuf Message
at
org.apache.geode.internal.protocol.protobuf.v1.serializer.ProtobufProtocolSerializer.deserialize(ProtobufProtocolSerializer.java:32)
at
org.apache.geode.internal.protocol.protobuf.v1.ProtobufStreamProcessor.processOneMessage(ProtobufStreamProcessor.java:65)
at
org.apache.geode.internal.protocol.protobuf.v1.ProtobufStreamProcessor.receiveMessage(ProtobufStreamProcessor.java:50)
at
org.apache.geode.internal.protocol.protobuf.v1.ProtobufCachePipeline.processMessage(ProtobufCachePipeline.java:44)
at
org.apache.geode.internal.cache.tier.sockets.ProtobufServerConnection.doOneMessage(ProtobufServerConnection.java:74)
at
org.apache.geode.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1248)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at
org.apache.geode.internal.cache.tier.sockets.AcceptorImpl$4$1.run(AcceptorImpl.java:644)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.net.SocketException: Socket closed
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
at java.net.SocketInputStream.read(SocketInputStream.java:171)
at java.net.SocketInputStream.read(SocketInputStream.java:141)
at java.net.SocketInputStream.read(SocketInputStream.java:224)
at
com.google.protobuf.AbstractParser.parsePartialDelimitedFrom(AbstractParser.java:253)
at
com.google.protobuf.AbstractParser.parseDelimitedFrom(AbstractParser.java:275)
at
com.google.protobuf.AbstractParser.parseDelimitedFrom(AbstractParser.java:280)
at
com.google.protobuf.AbstractParser.parseDelimitedFrom(AbstractParser.java:49)
at
com.google.protobuf.GeneratedMessageV3.parseDelimitedWithIOException(GeneratedMessageV3.java:347)
at
org.apache.geode.internal.protocol.protobuf.v1.ClientProtocol$Message.parseDelimitedFrom(ClientProtocol.java:2688)
at
org.apache.geode.internal.protocol.protobuf.v1.serializer.ProtobufProtocolSerializer.deserialize(ProtobufProtocolSerializer.java:30)
... 9 more
{code}
Component/s: client/server
Issue Type: Improvement (was: Bug)
Summary: Server logs exception from Protobuf connections when closing
(was: Server logs )
> Server logs exception from Protobuf connections when closing
>
>
> Key: GEODE-5229
> URL: https://issues.apache.org/jira/browse/GEODE-5229
> Project: Geode
> Issue Type: Improvement
> Components: client/server
>Reporter: Galen O'Sullivan
>Priority: Major
>
> I'm not sure whether this issue happens exclusively on shutdown, but it does
> happen reliably on shutdown when a connection from a Protobuf client is open,
> and the exception is logged per-connection, potentially leaving a lot in the
> logs. This happens despite the fix to GEODE-4300.
> {code}
> [info 2018/05/17 17:03:11.748 PDT tid=1] Cache server on port 21,497
> is shutting down.
> [info 2018/05/17 17:03:11.750 PDT
> tid=51] Invalid message
> org.apache.geode.internal.protocol.protobuf.v1.serializer.exception.InvalidProtocolMessageException:
> Failed to parse Protobuf Message
> at
> org.apache.geode.internal.protocol.protobuf.v1.serializer.ProtobufProtocolSerializer.deserialize(ProtobufProtocolSerializer.java:32)
> at
> org.apache.geode.internal.protocol.protobuf.v1.ProtobufStreamProcessor.processOneMessage(ProtobufStreamProcessor.java:65)
> at
> org.apache.geode.internal.protocol.protobuf.v1.ProtobufStreamProcessor.receiveMessage(ProtobufStreamProcessor.java:50)
> at
> org.apache.geode.internal.protocol.protobuf.v1.ProtobufCachePipeline.processMessage(ProtobufCachePipeline.java:44)
> at
> org.apache.geode.internal.cache.tier.sockets.ProtobufServerConnection.doOneMessage(ProtobufServerConnection.java:74)
> at
>
[jira] [Created] (GEODE-5229) Server logs
Galen O'Sullivan created GEODE-5229: --- Summary: Server logs Key: GEODE-5229 URL: https://issues.apache.org/jira/browse/GEODE-5229 Project: Geode Issue Type: Bug Reporter: Galen O'Sullivan -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-3698) New protocol EOF exception on client disconnect
[
https://issues.apache.org/jira/browse/GEODE-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Galen O'Sullivan resolved GEODE-3698.
-
Resolution: Duplicate
Fix Version/s: 1.5.0
I'm pretty sure this was fixed in GEODE-4300.
> New protocol EOF exception on client disconnect
> ---
>
> Key: GEODE-3698
> URL: https://issues.apache.org/jira/browse/GEODE-3698
> Project: Geode
> Issue Type: Bug
> Components: client/server
>Reporter: Brian Baynes
>Priority: Major
> Fix For: 1.5.0
>
>
> When a new protocol client closes the socket, looks like the server logs an
> EOF exception on a null message. Investigate ProtobufStreamProcessor and
> handling of client disconnects/null messages.
> [fine 2017/09/19 11:06:22.469 PDT s1 0> tid=0x4c] Encountered EOF while processing message: {}
> java.io.EOFException: Tried to deserialize protobuf message at EOF
> at
> org.apache.geode.protocol.protobuf.ProtobufStreamProcessor.processOneMessage(ProtobufStreamProcessor.java:84)
> at
> org.apache.geode.protocol.protobuf.ProtobufStreamProcessor.receiveMessage(ProtobufStreamProcessor.java:71)
> at
> org.apache.geode.internal.cache.tier.sockets.GenericProtocolServerConnection.doOneMessage(GenericProtocolServerConnection.java:78)
> at
> org.apache.geode.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1166)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at
> org.apache.geode.internal.cache.tier.sockets.AcceptorImpl$1$1.run(AcceptorImpl.java:557)
> at java.lang.Thread.run(Thread.java:745)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-1208) PersistentPartitionedRegionDUnitTest.testBug42226
[
https://issues.apache.org/jira/browse/GEODE-1208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16479824#comment-16479824
]
ASF subversion and git services commented on GEODE-1208:
Commit d6d97aaea4c5fef060ff918c8d85a85f3a7f123a in geode's branch
refs/heads/develop from [~apa...@the9muses.net]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=d6d97aa ]
GEODE-974: Fix PersistentPartitionedRegionDistributedTest
* Rename PersistentPartitionedRegionDUnitTest ->
PersistentPartitionedRegionDistributedTest
* Remove dependency on PersistentPartitionedRegionTestBase (GEODE-5175)
* Rename all test methods
* Overhaul test to use JUnit Rules, Awaitility and AssertJ
Fix all flaky issues in this test:
* GEODE-974: testRevokeBeforeStartup
* GEODE-1047: testMissingMemberRedundancy1
* GEODE-1208: testBug42226
* GEODE-1582: testCleanStop
* GEODE-1738: testCrashDuringBucketCreation
* GEODE-4418: testCleanupAfterConflict
> PersistentPartitionedRegionDUnitTest.testBug42226
> -
>
> Key: GEODE-1208
> URL: https://issues.apache.org/jira/browse/GEODE-1208
> Project: Geode
> Issue Type: Bug
> Components: persistence
>Reporter: Jinmei Liao
>Assignee: Kirk Lund
>Priority: Major
> Labels: CI, Flaky
>
> Geode_develop_DistributedTests/2215/
> Revision: 616bc27de8621224a9c7fba19a84dfc4eb4d520f
> {noformat}
> java.lang.Exception: An exception occured during async invocation
> at
> com.gemstone.gemfire.test.dunit.AsyncInvocation.getResult(AsyncInvocation.java:195)
> at
> com.gemstone.gemfire.internal.cache.partitioned.PersistentPartitionedRegionDUnitTest.testBug42226(PersistentPartitionedRegionDUnitTest.java:1701)
> 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 junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
> 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:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> at sun.reflect.GeneratedMethodAccessor396.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:106)
> at sun.reflect.GeneratedMethodAccessor395.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
>
[jira] [Commented] (GEODE-974) CI Failure: PersistentPartitionedRegionDUnitTest.testRevokeBeforeStartup failed with AssertionError
[
https://issues.apache.org/jira/browse/GEODE-974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16479820#comment-16479820
]
ASF subversion and git services commented on GEODE-974:
---
Commit d6d97aaea4c5fef060ff918c8d85a85f3a7f123a in geode's branch
refs/heads/develop from [~apa...@the9muses.net]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=d6d97aa ]
GEODE-974: Fix PersistentPartitionedRegionDistributedTest
* Rename PersistentPartitionedRegionDUnitTest ->
PersistentPartitionedRegionDistributedTest
* Remove dependency on PersistentPartitionedRegionTestBase (GEODE-5175)
* Rename all test methods
* Overhaul test to use JUnit Rules, Awaitility and AssertJ
Fix all flaky issues in this test:
* GEODE-974: testRevokeBeforeStartup
* GEODE-1047: testMissingMemberRedundancy1
* GEODE-1208: testBug42226
* GEODE-1582: testCleanStop
* GEODE-1738: testCrashDuringBucketCreation
* GEODE-4418: testCleanupAfterConflict
> CI Failure: PersistentPartitionedRegionDUnitTest.testRevokeBeforeStartup
> failed with AssertionError
> ---
>
> Key: GEODE-974
> URL: https://issues.apache.org/jira/browse/GEODE-974
> Project: Geode
> Issue Type: Bug
> Components: persistence
>Reporter: Barry Oglesby
>Assignee: Kirk Lund
>Priority: Major
> Labels: CI, Flaky, pull-request-available
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Geode_develop_DistributedTests
> Private Build #1602 (Feb 13, 2016 9:09:53 AM)
> Revision: 781277f31f37388f7247cbdf05025c12de825d2a
> Error Message
> {noformat}
> java.lang.AssertionError: Suspicious strings were written to the log during
> this run.
> Fix the strings or use DistributedTestCase.addExpectedException to ignore.
> ---
> Found suspect string in log4j at line 2919
> [fatal 2016/02/13 11:30:42.638 PST tid=0x580]
> Uncaught exception processing Alert "Error processing request class
> com.gemstone.gemfire.internal.admin.remote.PrepareRevokePersistentIDRequest."
> level ERROR
> java.lang.NullPointerException
> at
> com.gemstone.gemfire.internal.admin.remote.RemoteGfManagerAgent.getApplicationById(RemoteGfManagerAgent.java:606)
> at
> com.gemstone.gemfire.internal.admin.remote.RemoteGfManagerAgent.getMemberById(RemoteGfManagerAgent.java:592)
> at
> com.gemstone.gemfire.internal.admin.remote.AlertListenerMessage.process(AlertListenerMessage.java:83)
> at
> com.gemstone.gemfire.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:380)
> at
> com.gemstone.gemfire.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:451)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at
> com.gemstone.gemfire.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:656)
> at
> com.gemstone.gemfire.distributed.internal.DistributionManager$4$1.run(DistributionManager.java:930)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> Stacktrace
> {noformat}
> com.gemstone.gemfire.test.dunit.RMIException: While invoking
> com.gemstone.gemfire.management.internal.cli.commands.CliCommandTestBase$1.call
> in VM 0 running on Host cc4-rh6.gemstone.com with 4 VMs
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:372)
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:315)
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:281)
> at
> com.gemstone.gemfire.management.internal.cli.commands.CliCommandTestBase.createDefaultSetup(CliCommandTestBase.java:105)
> at
> com.gemstone.gemfire.management.internal.cli.commands.CreateAlterDestroyRegionCommandsDUnitTest.testCreateRegion46391(CreateAlterDestroyRegionCommandsDUnitTest.java:290)
> 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 junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at
[jira] [Commented] (GEODE-5175) Remove PersistentPartitionedRegionTestBase
[
https://issues.apache.org/jira/browse/GEODE-5175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16479821#comment-16479821
]
ASF subversion and git services commented on GEODE-5175:
Commit d6d97aaea4c5fef060ff918c8d85a85f3a7f123a in geode's branch
refs/heads/develop from [~apa...@the9muses.net]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=d6d97aa ]
GEODE-974: Fix PersistentPartitionedRegionDistributedTest
* Rename PersistentPartitionedRegionDUnitTest ->
PersistentPartitionedRegionDistributedTest
* Remove dependency on PersistentPartitionedRegionTestBase (GEODE-5175)
* Rename all test methods
* Overhaul test to use JUnit Rules, Awaitility and AssertJ
Fix all flaky issues in this test:
* GEODE-974: testRevokeBeforeStartup
* GEODE-1047: testMissingMemberRedundancy1
* GEODE-1208: testBug42226
* GEODE-1582: testCleanStop
* GEODE-1738: testCrashDuringBucketCreation
* GEODE-4418: testCleanupAfterConflict
> Remove PersistentPartitionedRegionTestBase
> --
>
> Key: GEODE-5175
> URL: https://issues.apache.org/jira/browse/GEODE-5175
> Project: Geode
> Issue Type: Improvement
> Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Minor
>
> Remove PersistentPartitionedRegionTestBase and overhaul the tests that extend
> it:
> {noformat}
> JUnit4DistributedTestCase (org.apache.geode.test.dunit.internal)
> JUnit4CacheTestCase (org.apache.geode.test.dunit.cache.internal)
> PersistentPartitionedRegionTestBase
> (org.apache.geode.internal.cache.partitioned)
> PersistentPartitionedRegionWithTransactionDUnitTest
> (org.apache.geode.internal.cache.partitioned)
> PersistentPartitionedRegionWithDistTXDUnitTest
> (org.apache.geode.disttx)
> PersistentColocatedPartitionedRegionDUnitTest
> (org.apache.geode.internal.cache.partitioned)
> PersistentPartitionedRegionDUnitTest
> (org.apache.geode.internal.cache.partitioned)
> PersistentPartitionedRegionOldConfigDUnitTest
> (org.apache.geode.internal.cache.partitioned)
> BackupDistributedTest (org.apache.geode.internal.cache.backup)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-1582) CI failure: PersistentPartitionedRegionOldConfigDUnitTest.testCleanStop
[ https://issues.apache.org/jira/browse/GEODE-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16479825#comment-16479825 ] ASF subversion and git services commented on GEODE-1582: Commit d6d97aaea4c5fef060ff918c8d85a85f3a7f123a in geode's branch refs/heads/develop from [~apa...@the9muses.net] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=d6d97aa ] GEODE-974: Fix PersistentPartitionedRegionDistributedTest * Rename PersistentPartitionedRegionDUnitTest -> PersistentPartitionedRegionDistributedTest * Remove dependency on PersistentPartitionedRegionTestBase (GEODE-5175) * Rename all test methods * Overhaul test to use JUnit Rules, Awaitility and AssertJ Fix all flaky issues in this test: * GEODE-974: testRevokeBeforeStartup * GEODE-1047: testMissingMemberRedundancy1 * GEODE-1208: testBug42226 * GEODE-1582: testCleanStop * GEODE-1738: testCrashDuringBucketCreation * GEODE-4418: testCleanupAfterConflict > CI failure: PersistentPartitionedRegionOldConfigDUnitTest.testCleanStop > --- > > Key: GEODE-1582 > URL: https://issues.apache.org/jira/browse/GEODE-1582 > Project: Geode > Issue Type: Bug > Components: persistence >Reporter: Hitesh Khamesra >Assignee: Kirk Lund >Priority: Major > Labels: CI, flaky > > https://brazil.gemstone.com:8080//job/Geode_develop_DistributedTests/2963/testReport/com.gemstone.gemfire.internal.cache.partitioned/PersistentPartitionedRegionOldConfigDUnitTest/testCleanStop > com.gemstone.gemfire.test.dunit.RMIException: While invoking > com.gemstone.gemfire.internal.cache.partitioned.PersistentPartitionedRegionTestBase$1.run > in VM 1 running on Host japan.gemstone.com with 4 VMs > Stacktrace > com.gemstone.gemfire.test.dunit.RMIException: While invoking > com.gemstone.gemfire.internal.cache.partitioned.PersistentPartitionedRegionTestBase$1.run > in VM 1 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.PersistentPartitionedRegionTestBase.checkRecoveredFromDisk(PersistentPartitionedRegionTestBase.java:100) > at > com.gemstone.gemfire.internal.cache.partitioned.PersistentPartitionedRegionDUnitTest.testCleanStop(PersistentPartitionedRegionDUnitTest.java:1353) > 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) >
[jira] [Commented] (GEODE-1047) CI failure: PersistentPartitionedRegionOldConfigDUnitTest.testMissingMemberRedundancy1
[ https://issues.apache.org/jira/browse/GEODE-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16479823#comment-16479823 ] ASF subversion and git services commented on GEODE-1047: Commit d6d97aaea4c5fef060ff918c8d85a85f3a7f123a in geode's branch refs/heads/develop from [~apa...@the9muses.net] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=d6d97aa ] GEODE-974: Fix PersistentPartitionedRegionDistributedTest * Rename PersistentPartitionedRegionDUnitTest -> PersistentPartitionedRegionDistributedTest * Remove dependency on PersistentPartitionedRegionTestBase (GEODE-5175) * Rename all test methods * Overhaul test to use JUnit Rules, Awaitility and AssertJ Fix all flaky issues in this test: * GEODE-974: testRevokeBeforeStartup * GEODE-1047: testMissingMemberRedundancy1 * GEODE-1208: testBug42226 * GEODE-1582: testCleanStop * GEODE-1738: testCrashDuringBucketCreation * GEODE-4418: testCleanupAfterConflict > CI failure: > PersistentPartitionedRegionOldConfigDUnitTest.testMissingMemberRedundancy1 > -- > > Key: GEODE-1047 > URL: https://issues.apache.org/jira/browse/GEODE-1047 > Project: Geode > Issue Type: Bug > Components: regions >Reporter: Jason Huynh >Assignee: Kirk Lund >Priority: Major > Labels: CI, Flaky > > junit.framework.AssertionFailedError: expected:<[]> but was:<[12]> > at junit.framework.Assert.fail(Assert.java:57) > at junit.framework.Assert.failNotEquals(Assert.java:329) > at junit.framework.Assert.assertEquals(Assert.java:78) > at junit.framework.Assert.assertEquals(Assert.java:86) > at junit.framework.TestCase.assertEquals(TestCase.java:253) > at > com.gemstone.gemfire.internal.cache.partitioned.PersistentPartitionedRegionDUnitTest.testMissingMemberRedundancy1(PersistentPartitionedRegionDUnitTest.java:1103) > 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 junit.framework.TestCase.runTest(TestCase.java:176) > at junit.framework.TestCase.runBare(TestCase.java:141) > at junit.framework.TestResult$1.protect(TestResult.java:122) > at junit.framework.TestResult.runProtected(TestResult.java:142) > at junit.framework.TestResult.run(TestResult.java:125) > at junit.framework.TestCase.run(TestCase.java:129) > at junit.framework.TestSuite.runTest(TestSuite.java:252) > at junit.framework.TestSuite.run(TestSuite.java:247) > at > org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105) > 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:64) > at > org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50) > 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:106) > 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
[jira] [Commented] (GEODE-1738) CI Failure: PersistentPartitionedRegionOldConfigDUnitTest.testCrashDuringBucketCreation CacheClosedException
[
https://issues.apache.org/jira/browse/GEODE-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16479826#comment-16479826
]
ASF subversion and git services commented on GEODE-1738:
Commit d6d97aaea4c5fef060ff918c8d85a85f3a7f123a in geode's branch
refs/heads/develop from [~apa...@the9muses.net]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=d6d97aa ]
GEODE-974: Fix PersistentPartitionedRegionDistributedTest
* Rename PersistentPartitionedRegionDUnitTest ->
PersistentPartitionedRegionDistributedTest
* Remove dependency on PersistentPartitionedRegionTestBase (GEODE-5175)
* Rename all test methods
* Overhaul test to use JUnit Rules, Awaitility and AssertJ
Fix all flaky issues in this test:
* GEODE-974: testRevokeBeforeStartup
* GEODE-1047: testMissingMemberRedundancy1
* GEODE-1208: testBug42226
* GEODE-1582: testCleanStop
* GEODE-1738: testCrashDuringBucketCreation
* GEODE-4418: testCleanupAfterConflict
> CI Failure:
> PersistentPartitionedRegionOldConfigDUnitTest.testCrashDuringBucketCreation
> CacheClosedException
>
>
> Key: GEODE-1738
> URL: https://issues.apache.org/jira/browse/GEODE-1738
> Project: Geode
> Issue Type: Bug
> Components: regions
>Affects Versions: 1.0.0-incubating
>Reporter: Scott Jewell
>Assignee: Kirk Lund
>Priority: Major
> Labels: ci, flaky
>
> GemFire Distributed Tests build 3526
> CacheClosedException
> {noformat}
> com.gemstone.gemfire.test.dunit.RMIException: While invoking
> com.gemstone.gemfire.internal.cache.partitioned.PersistentPartitionedRegionTestBase$14.run
> in VM 0 running on Host cc4-rh6.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.PersistentPartitionedRegionTestBase.createPR(PersistentPartitionedRegionTestBase.java:298)
> at
> com.gemstone.gemfire.internal.cache.partitioned.PersistentPartitionedRegionDUnitTest.testCrashDuringBucketCreation(PersistentPartitionedRegionDUnitTest.java:1514)
> 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:114)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
> 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
>
[jira] [Commented] (GEODE-4418) PersistentPartitionedRegionDUnitTest.testCleanupAfterConflict fails intermittently
[
https://issues.apache.org/jira/browse/GEODE-4418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16479827#comment-16479827
]
ASF subversion and git services commented on GEODE-4418:
Commit d6d97aaea4c5fef060ff918c8d85a85f3a7f123a in geode's branch
refs/heads/develop from [~apa...@the9muses.net]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=d6d97aa ]
GEODE-974: Fix PersistentPartitionedRegionDistributedTest
* Rename PersistentPartitionedRegionDUnitTest ->
PersistentPartitionedRegionDistributedTest
* Remove dependency on PersistentPartitionedRegionTestBase (GEODE-5175)
* Rename all test methods
* Overhaul test to use JUnit Rules, Awaitility and AssertJ
Fix all flaky issues in this test:
* GEODE-974: testRevokeBeforeStartup
* GEODE-1047: testMissingMemberRedundancy1
* GEODE-1208: testBug42226
* GEODE-1582: testCleanStop
* GEODE-1738: testCrashDuringBucketCreation
* GEODE-4418: testCleanupAfterConflict
> PersistentPartitionedRegionDUnitTest.testCleanupAfterConflict fails
> intermittently
> --
>
> Key: GEODE-4418
> URL: https://issues.apache.org/jira/browse/GEODE-4418
> Project: Geode
> Issue Type: Bug
> Components: persistence, regions
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Labels: Flaky
>
> {noformat}
> org.apache.geode.internal.cache.partitioned.PersistentPartitionedRegionDUnitTest
> > testCleanupAfterConflict FAILED
> java.lang.AssertionError: should have seen a conflicting data exception
> at org.junit.Assert.fail(Assert.java:88)
> at
> org.apache.geode.internal.cache.partitioned.PersistentPartitionedRegionDUnitTest.testCleanupAfterConflict(PersistentPartitionedRegionDUnitTest.java:2076)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-974) CI Failure: PersistentPartitionedRegionDUnitTest.testRevokeBeforeStartup failed with AssertionError
[
https://issues.apache.org/jira/browse/GEODE-974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16479822#comment-16479822
]
ASF subversion and git services commented on GEODE-974:
---
Commit d6d97aaea4c5fef060ff918c8d85a85f3a7f123a in geode's branch
refs/heads/develop from [~apa...@the9muses.net]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=d6d97aa ]
GEODE-974: Fix PersistentPartitionedRegionDistributedTest
* Rename PersistentPartitionedRegionDUnitTest ->
PersistentPartitionedRegionDistributedTest
* Remove dependency on PersistentPartitionedRegionTestBase (GEODE-5175)
* Rename all test methods
* Overhaul test to use JUnit Rules, Awaitility and AssertJ
Fix all flaky issues in this test:
* GEODE-974: testRevokeBeforeStartup
* GEODE-1047: testMissingMemberRedundancy1
* GEODE-1208: testBug42226
* GEODE-1582: testCleanStop
* GEODE-1738: testCrashDuringBucketCreation
* GEODE-4418: testCleanupAfterConflict
> CI Failure: PersistentPartitionedRegionDUnitTest.testRevokeBeforeStartup
> failed with AssertionError
> ---
>
> Key: GEODE-974
> URL: https://issues.apache.org/jira/browse/GEODE-974
> Project: Geode
> Issue Type: Bug
> Components: persistence
>Reporter: Barry Oglesby
>Assignee: Kirk Lund
>Priority: Major
> Labels: CI, Flaky, pull-request-available
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Geode_develop_DistributedTests
> Private Build #1602 (Feb 13, 2016 9:09:53 AM)
> Revision: 781277f31f37388f7247cbdf05025c12de825d2a
> Error Message
> {noformat}
> java.lang.AssertionError: Suspicious strings were written to the log during
> this run.
> Fix the strings or use DistributedTestCase.addExpectedException to ignore.
> ---
> Found suspect string in log4j at line 2919
> [fatal 2016/02/13 11:30:42.638 PST tid=0x580]
> Uncaught exception processing Alert "Error processing request class
> com.gemstone.gemfire.internal.admin.remote.PrepareRevokePersistentIDRequest."
> level ERROR
> java.lang.NullPointerException
> at
> com.gemstone.gemfire.internal.admin.remote.RemoteGfManagerAgent.getApplicationById(RemoteGfManagerAgent.java:606)
> at
> com.gemstone.gemfire.internal.admin.remote.RemoteGfManagerAgent.getMemberById(RemoteGfManagerAgent.java:592)
> at
> com.gemstone.gemfire.internal.admin.remote.AlertListenerMessage.process(AlertListenerMessage.java:83)
> at
> com.gemstone.gemfire.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:380)
> at
> com.gemstone.gemfire.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:451)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at
> com.gemstone.gemfire.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:656)
> at
> com.gemstone.gemfire.distributed.internal.DistributionManager$4$1.run(DistributionManager.java:930)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> Stacktrace
> {noformat}
> com.gemstone.gemfire.test.dunit.RMIException: While invoking
> com.gemstone.gemfire.management.internal.cli.commands.CliCommandTestBase$1.call
> in VM 0 running on Host cc4-rh6.gemstone.com with 4 VMs
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:372)
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:315)
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:281)
> at
> com.gemstone.gemfire.management.internal.cli.commands.CliCommandTestBase.createDefaultSetup(CliCommandTestBase.java:105)
> at
> com.gemstone.gemfire.management.internal.cli.commands.CreateAlterDestroyRegionCommandsDUnitTest.testCreateRegion46391(CreateAlterDestroyRegionCommandsDUnitTest.java:290)
> 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 junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at
[jira] [Commented] (GEODE-5002) Create a sub-module geode-test
[ https://issues.apache.org/jira/browse/GEODE-5002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16479749#comment-16479749 ] ASF subversion and git services commented on GEODE-5002: Commit da17cad3d5fd9dcd7e52cc263c4566df98ccc625 in geode's branch refs/heads/feature/GEODE-5145 from [~sai.boorlaga...@gmail.com] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=da17cad ] GEODE-5002: Create geode-test sub-module (#1965) moved JUnit categories from geode-junit to geode-test > Create a sub-module geode-test > -- > > Key: GEODE-5002 > URL: https://issues.apache.org/jira/browse/GEODE-5002 > Project: Geode > Issue Type: Task > Components: build >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > Time Spent: 2h 10m > Remaining Estimate: 0h > > Having dunit framework published to maven can enable users & developers to > write integration tests, especially for developers who intended to extend the > server side functionality. > * Create a new sub-module `geode-test` > * Move dunit framework, junit rules and related classes to this sub-module > * Publish geode-test artifact to maven -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5195) RegionMapPutTest should cover all the code in RegionMapPut
[ https://issues.apache.org/jira/browse/GEODE-5195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16479750#comment-16479750 ] ASF subversion and git services commented on GEODE-5195: Commit 586d7c3076cce04f66ab3d975f3b4eccbe6b1c67 in geode's branch refs/heads/feature/GEODE-5145 from [~dschneider] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=586d7c3 ] GEODE-5195: add unit tests for RegionMapPut (#1964) > RegionMapPutTest should cover all the code in RegionMapPut > -- > > Key: GEODE-5195 > URL: https://issues.apache.org/jira/browse/GEODE-5195 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > The RegionMapPutTest unit test does not test all the code in the RegionMapPut > class. > It should be improved to cover the entire class. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5145) Lucene index needs to support being destroyed while region is being created
[ https://issues.apache.org/jira/browse/GEODE-5145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16479755#comment-16479755 ] ASF subversion and git services commented on GEODE-5145: Commit 4a58d458b9f711a8a0b1592796f4d4db83de853e in geode's branch refs/heads/feature/GEODE-5145 from [~barry.oglesby] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=4a58d45 ] GEODE-5145: Incorporated review comments > Lucene index needs to support being destroyed while region is being created > --- > > Key: GEODE-5145 > URL: https://issues.apache.org/jira/browse/GEODE-5145 > Project: Geode > Issue Type: Bug > Components: lucene >Reporter: Barry Oglesby >Priority: Major > Labels: pull-request-available > Time Spent: 1h 20m > Remaining Estimate: 0h > > Attempting to destroy a lucene index while the region is being created may > leave the lucene service in an inconsistent state. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5218) Update docs on Log4j 2
[ https://issues.apache.org/jira/browse/GEODE-5218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16479752#comment-16479752 ] ASF subversion and git services commented on GEODE-5218: Commit b41e4af3e28f0e4f29896dabac2a4794b277caf9 in geode's branch refs/heads/feature/GEODE-5145 from Karen Miller [ https://gitbox.apache.org/repos/asf?p=geode.git;h=b41e4af ] GEODE-5218 Update docs with Log4j 2 version (#1963) > Update docs on Log4j 2 > -- > > Key: GEODE-5218 > URL: https://issues.apache.org/jira/browse/GEODE-5218 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Karen Smoler Miller >Assignee: Karen Smoler Miller >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Our docs still mention Log4j version 2.1. Time to update. While we're > updating, fix the specification of the JAR location. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4858) refactor internal commands to use the public ClusterConfigService
[ https://issues.apache.org/jira/browse/GEODE-4858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16479753#comment-16479753 ] ASF subversion and git services commented on GEODE-4858: Commit 085078f942dcc3cae24a445e7a8f8685ecd25a94 in geode's branch refs/heads/feature/GEODE-5145 from [~jens.deppe] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=085078f ] GEODE-4858: Convert DestroyIndexCommand to ResultModel and new cluster persistence API (#1966) > refactor internal commands to use the public ClusterConfigService > - > > Key: GEODE-4858 > URL: https://issues.apache.org/jira/browse/GEODE-4858 > Project: Geode > Issue Type: Sub-task > Components: configuration >Reporter: Jinmei Liao >Priority: Major > Labels: pull-request-available > Time Spent: 14h 40m > Remaining Estimate: 0h > > # except the ones that would need to access the internal cluster > configuration regions, like importClusterConfigCommand, > exportClusterConfigCommand or deploy > # use the configuration object as much as possible to pass parameters to the > functions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5145) Lucene index needs to support being destroyed while region is being created
[ https://issues.apache.org/jira/browse/GEODE-5145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16479754#comment-16479754 ] ASF subversion and git services commented on GEODE-5145: Commit 397ebaa419a3c48e1c18a00b145e930b66e82d23 in geode's branch refs/heads/feature/GEODE-5145 from [~barry.oglesby] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=397ebaa ] GEODE-5145: Added support for destroying an index during region creation > Lucene index needs to support being destroyed while region is being created > --- > > Key: GEODE-5145 > URL: https://issues.apache.org/jira/browse/GEODE-5145 > Project: Geode > Issue Type: Bug > Components: lucene >Reporter: Barry Oglesby >Priority: Major > Labels: pull-request-available > Time Spent: 1h 20m > Remaining Estimate: 0h > > Attempting to destroy a lucene index while the region is being created may > leave the lucene service in an inconsistent state. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5011) Refactor Commands to use *ResultModel
[ https://issues.apache.org/jira/browse/GEODE-5011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16479744#comment-16479744 ] ASF subversion and git services commented on GEODE-5011: Commit 22456961f92b909993fa8f7e68d30e3b9fec9a35 in geode's branch refs/heads/feature/GEODE-5145 from [~jens.deppe] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=2245696 ] GEODE-5185 and GEODE-5011: Fix test failures introduced by race on committing > Refactor Commands to use *ResultModel > - > > Key: GEODE-5011 > URL: https://issues.apache.org/jira/browse/GEODE-5011 > Project: Geode > Issue Type: Sub-task > Components: gfsh >Reporter: Jens Deppe >Priority: Major > Labels: pull-request-available > Time Spent: 2h 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5011) Refactor Commands to use *ResultModel
[ https://issues.apache.org/jira/browse/GEODE-5011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16479745#comment-16479745 ] ASF subversion and git services commented on GEODE-5011: Commit bf0d41de4490de74653a80218075464bf98237a3 in geode's branch refs/heads/feature/GEODE-5145 from [~jens.deppe] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=bf0d41d ] GEODE-5011: Status IGNORED is correctly processed in conjunction with ignoreIfFailed > Refactor Commands to use *ResultModel > - > > Key: GEODE-5011 > URL: https://issues.apache.org/jira/browse/GEODE-5011 > Project: Geode > Issue Type: Sub-task > Components: gfsh >Reporter: Jens Deppe >Priority: Major > Labels: pull-request-available > Time Spent: 2h 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5185) Correct recent backward-compatibility violation in 'create gateway-receiver' command.
[
https://issues.apache.org/jira/browse/GEODE-5185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16479743#comment-16479743
]
ASF subversion and git services commented on GEODE-5185:
Commit 22456961f92b909993fa8f7e68d30e3b9fec9a35 in geode's branch
refs/heads/feature/GEODE-5145 from [~jens.deppe]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=2245696 ]
GEODE-5185 and GEODE-5011: Fix test failures introduced by race on committing
> Correct recent backward-compatibility violation in 'create gateway-receiver'
> command.
> -
>
> Key: GEODE-5185
> URL: https://issues.apache.org/jira/browse/GEODE-5185
> Project: Geode
> Issue Type: Bug
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Commit {{4dff0cde9c3abca2dad03897c055e9c443a81b60}} changed {{create
> gateway-receiver}} to fail if any server fails to create the gateway receiver
> when the {{if-not-exists}} command is not given. This is inconsistent with
> the expected behavior of previous minor releases.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-5194) Relax Gfsh version checking on connect, allow connecting to different patch versions
[
https://issues.apache.org/jira/browse/GEODE-5194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barbara Pruijn resolved GEODE-5194.
---
Resolution: Fixed
> Relax Gfsh version checking on connect, allow connecting to different patch
> versions
>
>
> Key: GEODE-5194
> URL: https://issues.apache.org/jira/browse/GEODE-5194
> Project: Geode
> Issue Type: Improvement
> Components: gfsh
>Reporter: Kenneth Howe
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently Gfsh, {{connect}} command will only connect to locator with the
> same exact version. Patch versions should not add or change functionality of
> commands, so for Gfsh version {{x.y.z}} connection to locator with same major
> and minor, {{x.y}}, version with a different patch, {{.z}}, should be allowed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4858) refactor internal commands to use the public ClusterConfigService
[ https://issues.apache.org/jira/browse/GEODE-4858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16479628#comment-16479628 ] ASF subversion and git services commented on GEODE-4858: Commit 9203ccd1a8fe6006b7a6e9e0f8ebcd8145a2ca99 in geode's branch refs/heads/develop from [~khowe] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=9203ccd ] GEODE-4858: Refactor destroy gateway-receiver command (#1968) * GEODE-4858: Refactor destroy gateway-receiver command Refactored to use SingleGfshCommand and ResultModel Added tests for more complete unit test coverage of DestroyGatewayReceiverFuntion > refactor internal commands to use the public ClusterConfigService > - > > Key: GEODE-4858 > URL: https://issues.apache.org/jira/browse/GEODE-4858 > Project: Geode > Issue Type: Sub-task > Components: configuration >Reporter: Jinmei Liao >Priority: Major > Labels: pull-request-available > Time Spent: 14h 40m > Remaining Estimate: 0h > > # except the ones that would need to access the internal cluster > configuration regions, like importClusterConfigCommand, > exportClusterConfigCommand or deploy > # use the configuration object as much as possible to pass parameters to the > functions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4858) refactor internal commands to use the public ClusterConfigService
[ https://issues.apache.org/jira/browse/GEODE-4858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16479629#comment-16479629 ] ASF subversion and git services commented on GEODE-4858: Commit 9203ccd1a8fe6006b7a6e9e0f8ebcd8145a2ca99 in geode's branch refs/heads/develop from [~khowe] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=9203ccd ] GEODE-4858: Refactor destroy gateway-receiver command (#1968) * GEODE-4858: Refactor destroy gateway-receiver command Refactored to use SingleGfshCommand and ResultModel Added tests for more complete unit test coverage of DestroyGatewayReceiverFuntion > refactor internal commands to use the public ClusterConfigService > - > > Key: GEODE-4858 > URL: https://issues.apache.org/jira/browse/GEODE-4858 > Project: Geode > Issue Type: Sub-task > Components: configuration >Reporter: Jinmei Liao >Priority: Major > Labels: pull-request-available > Time Spent: 14h 40m > Remaining Estimate: 0h > > # except the ones that would need to access the internal cluster > configuration regions, like importClusterConfigCommand, > exportClusterConfigCommand or deploy > # use the configuration object as much as possible to pass parameters to the > functions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4728) Geode Native Documentation Improvements
[ https://issues.apache.org/jira/browse/GEODE-4728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16479585#comment-16479585 ] ASF subversion and git services commented on GEODE-4728: Commit ecd5caf93388e0739d2c632c6bf96b21d5ce6fde in geode-native's branch refs/heads/develop from [~dbarnes97] [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=ecd5caf ] GEODE-4728: Docs - format improvements, cache config page > Geode Native Documentation Improvements > --- > > Key: GEODE-4728 > URL: https://issues.apache.org/jira/browse/GEODE-4728 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Addison >Priority: Major > Labels: pull-request-available > Time Spent: 2h 50m > Remaining Estimate: 0h > > This ticket will capture a series of changes to the Geode Native docs to > bring them inline with the updated API. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5186) set operation in a client transaction could cause the transaction to hang
[
https://issues.apache.org/jira/browse/GEODE-5186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-5186:
--
Labels: pull-request-available (was: )
> set operation in a client transaction could cause the transaction to hang
> -
>
> Key: GEODE-5186
> URL: https://issues.apache.org/jira/browse/GEODE-5186
> Project: Geode
> Issue Type: Bug
> Components: transactions
>Affects Versions: 1.1.0, 1.1.1, 1.2.0, 1.3.0, 1.2.1, 1.4.0, 1.5.0, 1.6.0
>Reporter: Eric Shu
>Priority: Major
> Labels: pull-request-available
>
> During an entry operation in a client transaction, server connection could be
> lost. In this case, client will failover to another server and try to resume
> the transaction and retry the operation if the original transaction host node
> is found.
> If this operation happens to be a keySet operation (or other set operations)
> on a partitioned region, the transaction could hang due to a deadlock.
> The scenario is the original tx host node holds its transactional lock when
> sending fetchKey request to other nodes hosting the partitioned region data.
> The node on which the client transaction failed over, will hold its
> transactional lock while sending the FetchKey message to transaction hosting
> node.
> These two FetchKeyMessage will not be able to be processed as processing
> these tx message requires to hold the lock. But the locks are already been
> held by the nodes handing the client message of the transaction.
> {noformat}
> vm_6_bridge7_latvia_25133:PartitionedRegion Message Processor10 ID=0xe2(226)
> state=WAITING
> waiting to lock
>
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:870)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1199)
> at
> java.util.concurrent.locks.ReentrantLock$NonfairSync.lock(ReentrantLock.java:209)
> at
> java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock.java:285)
> at
> org.apache.geode.internal.cache.TXManagerImpl.getLock(TXManagerImpl.java:921)
> at
> org.apache.geode.internal.cache.TXManagerImpl.masqueradeAs(TXManagerImpl.java:881)
> at
> org.apache.geode.internal.cache.partitioned.PartitionMessage.process(PartitionMessage.java:332)
> at
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:378)
> at
> org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:444)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.runUntilShutdown(ClusterDistributionManager.java:1121)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.access$000(ClusterDistributionManager.java:109)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager$8$1.run(ClusterDistributionManager.java:945)
> at java.lang.Thread.run(Thread.java:745)
> Locked synchronizers:
> java.util.concurrent.ThreadPoolExecutor$Worker@c84d7d4
> vm_6_bridge7_latvia_25133:ServerConnection on port 23931 Thread 10
> ID=0x128(296) state=TIMED_WAITING
> waiting to lock
> at sun.misc.Unsafe.park(Native Method)
> at
> java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1037)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1328)
> at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:277)
> at
> org.apache.geode.internal.util.concurrent.StoppableCountDownLatch.await(StoppableCountDownLatch.java:61)
> at
> org.apache.geode.distributed.internal.ReplyProcessor21.basicWait(ReplyProcessor21.java:715)
> at
> org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:790)
> at
>
[jira] [Updated] (GEODE-3845) Distributed destroy on eviction
[
https://issues.apache.org/jira/browse/GEODE-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Vallely updated GEODE-3845:
Description:
I use entry-idle-time and eviction together in a partition region that holds
one redundant copy.
Details of setting are as follows:
{code:xml}
{code}
In this setting, the data held by the cache server is different. Then,
inconsistent results are returned depending on the server to be connected.
Eviction of the partition region can only select local-destroy or
overflow-to-disk. On the other hand, it is written that the expire chapter of
the document can not use local-destroy, local-invalidate in the partition
region. Likewise, I think that data inconsistency will occur even with the
settings like this time.
Below is the test code:
[https://github.com/masaki-yamakawa/geode/blob/bug-partition-local-destroy/geode-core/src/test/java/org/apache/geode/internal/cache/partitioned/BugExpireAndEvictionDUnitTest.java]
I think that it is necessary to add a check at the time of region creation or
write it in the document.
**
Problem: currently eviction-action must be either 'local-destroy' or
'overflow-to-disk'
ex:
Solution: This story is to add the additional option "distributed-destroy" as
an action setting for any eviction type.
This will enable a local destroy action to be distributed across the cluster
(currently this does not exist)
Acceptance: can set this on region configuration via cache.xml, API or gfsh
gfsh help and docs have been updated
was:
I use entry-idle-time and eviction together in a partition region that holds
one redundant copy.
Details of setting are as follows:
{code:xml}
{code}
In this setting, the data held by the cache server is different. Then,
inconsistent results are returned depending on the server to be connected.
Eviction of the partition region can only select local-destroy or
overflow-to-disk. On the other hand, it is written that the expire chapter of
the document can not use local-destroy, local-invalidate in the partition
region. Likewise, I think that data inconsistency will occur even with the
settings like this time.
Below is the test code:
[https://github.com/masaki-yamakawa/geode/blob/bug-partition-local-destroy/geode-core/src/test/java/org/apache/geode/internal/cache/partitioned/BugExpireAndEvictionDUnitTest.java]
I think that it is necessary to add a check at the time of region creation or
write it in the document.
**
Problem: currently eviction-action must be either 'local-destroy' or
'overflow-to-disk'
ex:
Solution: This story is to add the additional option "distributed-destroy" as
an action setting for any eviction type.
This will enable a local destroy action to be distributed across the cluster
(currently this does not exist)
Acceptance: can set this on region configuration via cache.xml, API or gfsh
gfsh help and docs have been updated
+Story: Add Option+
Given I want data consistency across a distributed replicated region
When I go to set an eviction action
Then I should have the ability to specify one of the following actions:
* 'local-destroy' [Default action]
* 'none'
* 'overflow-to-disk'
* 'distributed-destroy' (NEW option)
+Story: Behavior+
Given I have a region expiration action set in the system to
'distributed-destroy'
When an eviction event based on [mem%, count, regionSize, time] occurs to
destroy entries
Then the system will destroy the same entries in any region where they exist
across the distributed environment
+Story: Configuring cache.xml+
Given I am configuring a system with replicated regions
When I setup my cache.xml
Then I have the ability to add a 'destributed–destroy' action value for the
following tags:
*
+Story: Spring Data Gemfire+
Given I am configuring a system with replicated regions
when I setup my region's eviction action through Spring Data Gemfire
Then I need the ability to specify the value of 'distributed-destroy'
+Story : Documentation+
Given I am looking for help for region configuration
When I look at the help documentation for 'Configure Data Eviction'
Then I should see details under the 'Decide what action to take when the limit
is reached' section for 'Distributed Destroy'
+Story: GFSH Create region+
GIVEN I want to create a new region with distributed-destroy eviction-action
through GFSH CLI
WHEN I use the command
{code:java}
create region{code}
THEN I have the optional parameter of
{code:java}
--eviction-action=distributed-destroy{code}
AND the API utilized by GFSH is updated to support this value for create region
> Distributed destroy on eviction
> ---
>
> Key: GEODE-3845
> URL: https://issues.apache.org/jira/browse/GEODE-3845
>
[jira] [Updated] (GEODE-5228) ServerLauncherRemoteFileIntegrationTest fails intermittently with IllegalStateException vf.gf.server.status is blank
[
https://issues.apache.org/jira/browse/GEODE-5228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-5228:
-
Labels: ServerLauncher ci flaky (was: ci flaky)
> ServerLauncherRemoteFileIntegrationTest fails intermittently with
> IllegalStateException vf.gf.server.status is blank
>
>
> Key: GEODE-5228
> URL: https://issues.apache.org/jira/browse/GEODE-5228
> Project: Geode
> Issue Type: Bug
> Components: management, tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Minor
> Labels: ServerLauncher, ci, flaky
>
> {noformat}
> java.lang.IllegalStateException: Status file
> '/tmp/build/ae3c03f4/built-geode/tmp/junit5775773082469887234/vf.gf.server.status'
> is blank
> at
> org.apache.geode.internal.process.FileProcessController.status(FileProcessController.java:152)
> at
> org.apache.geode.internal.process.FileProcessController.status(FileProcessController.java:89)
> at
> org.apache.geode.distributed.ServerLauncher.statusWithWorkingDirectory(ServerLauncher.java:1102)
> at
> org.apache.geode.distributed.ServerLauncher.status(ServerLauncher.java:1050)
> at
> org.apache.geode.distributed.ServerLauncherRemoteIntegrationTestCase.lambda$awaitStart$1(ServerLauncherRemoteIntegrationTestCase.java:198)
> at
> org.awaitility.core.AssertionCondition$1.eval(AssertionCondition.java:55)
> at
> org.awaitility.core.ConditionAwaiter$ConditionPoller.run(ConditionAwaiter.java:215)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 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
(v7.6.3#76005)
[jira] [Assigned] (GEODE-5228) ServerLauncherRemoteFileIntegrationTest fails intermittently with IllegalStateException vf.gf.server.status is blank
[
https://issues.apache.org/jira/browse/GEODE-5228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund reassigned GEODE-5228:
Assignee: Kirk Lund
> ServerLauncherRemoteFileIntegrationTest fails intermittently with
> IllegalStateException vf.gf.server.status is blank
>
>
> Key: GEODE-5228
> URL: https://issues.apache.org/jira/browse/GEODE-5228
> Project: Geode
> Issue Type: Bug
> Components: management, tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Minor
> Labels: ci, flaky
>
> {noformat}
> java.lang.IllegalStateException: Status file
> '/tmp/build/ae3c03f4/built-geode/tmp/junit5775773082469887234/vf.gf.server.status'
> is blank
> at
> org.apache.geode.internal.process.FileProcessController.status(FileProcessController.java:152)
> at
> org.apache.geode.internal.process.FileProcessController.status(FileProcessController.java:89)
> at
> org.apache.geode.distributed.ServerLauncher.statusWithWorkingDirectory(ServerLauncher.java:1102)
> at
> org.apache.geode.distributed.ServerLauncher.status(ServerLauncher.java:1050)
> at
> org.apache.geode.distributed.ServerLauncherRemoteIntegrationTestCase.lambda$awaitStart$1(ServerLauncherRemoteIntegrationTestCase.java:198)
> at
> org.awaitility.core.AssertionCondition$1.eval(AssertionCondition.java:55)
> at
> org.awaitility.core.ConditionAwaiter$ConditionPoller.run(ConditionAwaiter.java:215)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 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
(v7.6.3#76005)
[jira] [Updated] (GEODE-5228) ServerLauncherRemoteFileIntegrationTest fails intermittently with IllegalStateException vf.gf.server.status is blank
[
https://issues.apache.org/jira/browse/GEODE-5228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-5228:
-
Priority: Minor (was: Major)
> ServerLauncherRemoteFileIntegrationTest fails intermittently with
> IllegalStateException vf.gf.server.status is blank
>
>
> Key: GEODE-5228
> URL: https://issues.apache.org/jira/browse/GEODE-5228
> Project: Geode
> Issue Type: Bug
> Components: management, tests
>Reporter: Kirk Lund
>Priority: Minor
> Labels: ci, flaky
>
> {noformat}
> java.lang.IllegalStateException: Status file
> '/tmp/build/ae3c03f4/built-geode/tmp/junit5775773082469887234/vf.gf.server.status'
> is blank
> at
> org.apache.geode.internal.process.FileProcessController.status(FileProcessController.java:152)
> at
> org.apache.geode.internal.process.FileProcessController.status(FileProcessController.java:89)
> at
> org.apache.geode.distributed.ServerLauncher.statusWithWorkingDirectory(ServerLauncher.java:1102)
> at
> org.apache.geode.distributed.ServerLauncher.status(ServerLauncher.java:1050)
> at
> org.apache.geode.distributed.ServerLauncherRemoteIntegrationTestCase.lambda$awaitStart$1(ServerLauncherRemoteIntegrationTestCase.java:198)
> at
> org.awaitility.core.AssertionCondition$1.eval(AssertionCondition.java:55)
> at
> org.awaitility.core.ConditionAwaiter$ConditionPoller.run(ConditionAwaiter.java:215)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 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
(v7.6.3#76005)
[jira] [Updated] (GEODE-5228) ServerLauncherRemoteFileIntegrationTest fails intermittently with IllegalStateException vf.gf.server.status is blank
[
https://issues.apache.org/jira/browse/GEODE-5228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-5228:
-
Labels: ci flaky (was: )
> ServerLauncherRemoteFileIntegrationTest fails intermittently with
> IllegalStateException vf.gf.server.status is blank
>
>
> Key: GEODE-5228
> URL: https://issues.apache.org/jira/browse/GEODE-5228
> Project: Geode
> Issue Type: Bug
> Components: management, tests
>Reporter: Kirk Lund
>Priority: Major
> Labels: ci, flaky
>
> {noformat}
> java.lang.IllegalStateException: Status file
> '/tmp/build/ae3c03f4/built-geode/tmp/junit5775773082469887234/vf.gf.server.status'
> is blank
> at
> org.apache.geode.internal.process.FileProcessController.status(FileProcessController.java:152)
> at
> org.apache.geode.internal.process.FileProcessController.status(FileProcessController.java:89)
> at
> org.apache.geode.distributed.ServerLauncher.statusWithWorkingDirectory(ServerLauncher.java:1102)
> at
> org.apache.geode.distributed.ServerLauncher.status(ServerLauncher.java:1050)
> at
> org.apache.geode.distributed.ServerLauncherRemoteIntegrationTestCase.lambda$awaitStart$1(ServerLauncherRemoteIntegrationTestCase.java:198)
> at
> org.awaitility.core.AssertionCondition$1.eval(AssertionCondition.java:55)
> at
> org.awaitility.core.ConditionAwaiter$ConditionPoller.run(ConditionAwaiter.java:215)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 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
(v7.6.3#76005)
[jira] [Created] (GEODE-5228) ServerLauncherRemoteFileIntegrationTest fails intermittently with IllegalStateException vf.gf.server.status is blank
Kirk Lund created GEODE-5228:
Summary: ServerLauncherRemoteFileIntegrationTest fails
intermittently with IllegalStateException vf.gf.server.status is blank
Key: GEODE-5228
URL: https://issues.apache.org/jira/browse/GEODE-5228
Project: Geode
Issue Type: Bug
Components: management, tests
Reporter: Kirk Lund
{noformat}
java.lang.IllegalStateException: Status file
'/tmp/build/ae3c03f4/built-geode/tmp/junit5775773082469887234/vf.gf.server.status'
is blank
at
org.apache.geode.internal.process.FileProcessController.status(FileProcessController.java:152)
at
org.apache.geode.internal.process.FileProcessController.status(FileProcessController.java:89)
at
org.apache.geode.distributed.ServerLauncher.statusWithWorkingDirectory(ServerLauncher.java:1102)
at
org.apache.geode.distributed.ServerLauncher.status(ServerLauncher.java:1050)
at
org.apache.geode.distributed.ServerLauncherRemoteIntegrationTestCase.lambda$awaitStart$1(ServerLauncherRemoteIntegrationTestCase.java:198)
at
org.awaitility.core.AssertionCondition$1.eval(AssertionCondition.java:55)
at
org.awaitility.core.ConditionAwaiter$ConditionPoller.run(ConditionAwaiter.java:215)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
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
(v7.6.3#76005)
[jira] [Updated] (GEODE-3845) Distributed destroy on eviction
[
https://issues.apache.org/jira/browse/GEODE-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Vallely updated GEODE-3845:
Summary: Distributed destroy on eviction (was: Distributed destroy for
replicated region)
> Distributed destroy on eviction
> ---
>
> Key: GEODE-3845
> URL: https://issues.apache.org/jira/browse/GEODE-3845
> Project: Geode
> Issue Type: New Feature
> Components: docs, eviction
>Reporter: Masaki Yamakawa
>Priority: Major
>
> I use entry-idle-time and eviction together in a partition region that holds
> one redundant copy.
> Details of setting are as follows:
> {code:xml}
>
>
>
>
>
>
>
>
>
>
>
> {code}
> In this setting, the data held by the cache server is different. Then,
> inconsistent results are returned depending on the server to be connected.
> Eviction of the partition region can only select local-destroy or
> overflow-to-disk. On the other hand, it is written that the expire chapter of
> the document can not use local-destroy, local-invalidate in the partition
> region. Likewise, I think that data inconsistency will occur even with the
> settings like this time.
> Below is the test code:
> [https://github.com/masaki-yamakawa/geode/blob/bug-partition-local-destroy/geode-core/src/test/java/org/apache/geode/internal/cache/partitioned/BugExpireAndEvictionDUnitTest.java]
> I think that it is necessary to add a check at the time of region creation or
> write it in the document.
>
> **
> Problem: currently eviction-action must be either 'local-destroy' or
> 'overflow-to-disk'
> ex:
> Solution: This story is to add the additional option "distributed-destroy" as
> an action setting for any eviction type.
> This will enable a local destroy action to be distributed across the cluster
> (currently this does not exist)
>
> Acceptance: can set this on region configuration via cache.xml, API or gfsh
> gfsh help and docs have been updated
>
> +Story: Add Option+
> Given I want data consistency across a distributed replicated region
> When I go to set an eviction action
> Then I should have the ability to specify one of the following actions:
> * 'local-destroy' [Default action]
> * 'none'
> * 'overflow-to-disk'
> * 'distributed-destroy' (NEW option)
>
> +Story: Behavior+
>
> Given I have a region expiration action set in the system to
> 'distributed-destroy'
> When an eviction event based on [mem%, count, regionSize, time] occurs to
> destroy entries
> Then the system will destroy the same entries in any region where they exist
> across the distributed environment
>
> +Story: Configuring cache.xml+
> Given I am configuring a system with replicated regions
> When I setup my cache.xml
> Then I have the ability to add a 'destributed–destroy' action value for the
> following tags:
> *
>
>
> +Story: Spring Data Gemfire+
> Given I am configuring a system with replicated regions
> when I setup my region's eviction action through Spring Data Gemfire
> Then I need the ability to specify the value of 'distributed-destroy'
>
> +Story : Documentation+
> Given I am looking for help for region configuration
> When I look at the help documentation for 'Configure Data Eviction'
> Then I should see details under the 'Decide what action to take when the
> limit is reached' section for 'Distributed Destroy'
>
> +Story: GFSH Create region+
> GIVEN I want to create a new region with distributed-destroy eviction-action
> through GFSH CLI
> WHEN I use the command
> {code:java}
> create region{code}
> THEN I have the optional parameter of
> {code:java}
> --eviction-action=distributed-destroy{code}
> AND the API utilized by GFSH is updated to support this value for create
> region
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5226) Decouple BaseCommand from response writing and exception handling
[
https://issues.apache.org/jira/browse/GEODE-5226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dale Emery updated GEODE-5226:
--
Priority: Minor (was: Major)
> Decouple BaseCommand from response writing and exception handling
> -
>
> Key: GEODE-5226
> URL: https://issues.apache.org/jira/browse/GEODE-5226
> Project: Geode
> Issue Type: Improvement
> Components: regions
>Reporter: Dale Emery
>Priority: Minor
>
> To facilitate testing, provide an easier way to verify that each command
> sends the appropriate responses.
> Currently, the responsibility to write and send responses, and the
> responsibility to handle and report exceptions, are implemented as static
> methods on {{BaseCommand}}. The static methods are difficult to fake for
> testing purposes, to test that individual commands send replies and handle
> exceptions properly.
> So: Extract some or all of the response-writing ({{writeXXX}}) and
> exception-handling ({{handleXXX}}) methods from {{BaseCommand}} into one or
> more classes focused on those responsibilities. Give {{BaseCommand}} and its
> subclasses a factory to construct any response-writer and/or
> exception-handler instances.
> As needed, add constructors to allow tests to supply test-specific factories
> for the helpers. Tests can create fake helpers (such as mocks) that are easy
> to control and observe.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4858) refactor internal commands to use the public ClusterConfigService
[ https://issues.apache.org/jira/browse/GEODE-4858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16479018#comment-16479018 ] ASF subversion and git services commented on GEODE-4858: Commit 085078f942dcc3cae24a445e7a8f8685ecd25a94 in geode's branch refs/heads/develop from [~jens.deppe] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=085078f ] GEODE-4858: Convert DestroyIndexCommand to ResultModel and new cluster persistence API (#1966) > refactor internal commands to use the public ClusterConfigService > - > > Key: GEODE-4858 > URL: https://issues.apache.org/jira/browse/GEODE-4858 > Project: Geode > Issue Type: Sub-task > Components: configuration >Reporter: Jinmei Liao >Priority: Major > Labels: pull-request-available > Time Spent: 14h 10m > Remaining Estimate: 0h > > # except the ones that would need to access the internal cluster > configuration regions, like importClusterConfigCommand, > exportClusterConfigCommand or deploy > # use the configuration object as much as possible to pass parameters to the > functions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
