[jira] [Commented] (GEODE-9060) checkMyStateOnMemebers is better not to change the replicates
[ https://issues.apache.org/jira/browse/GEODE-9060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468280#comment-17468280 ] ASF subversion and git services commented on GEODE-9060: Commit 1e2b384fdd43d6ddd5226d9b6fb18d88bb70fd98 in geode's branch refs/heads/support/1.12 from Xiaojian Zhou [ https://gitbox.apache.org/repos/asf?p=geode.git;h=1e2b384 ] GEODE-9060: Remove the member from a copy of replicates as GII candid… (#6246) * GEODE-9060: Remove the member from a copy of replicates as GII candidate if it's not part of the same distributed system, but leave original replicates unchanged. (cherry picked from commit 76a5afddc9eaecea9f0b4528a910eb6761e1a3a1) > checkMyStateOnMemebers is better not to change the replicates > - > > Key: GEODE-9060 > URL: https://issues.apache.org/jira/browse/GEODE-9060 > Project: Geode > Issue Type: Bug >Reporter: Xiaojian Zhou >Assignee: Xiaojian Zhou >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > Fix For: 1.12.8, 1.13.7, 1.14.3, 1.15.0 > > > This is an enhancement to previous GEODE-9003. > The previous fix will remove the members in replicates if it cannot recognize > current member, thus these removed members will not acting as GII provider > candidates. The fix is correct. > However, Dan suggested to keep the replicates as is to be more conservative. > These members will still act as GII provider candidates even they cannot > recognize current member due to the split-brain. Conceptually these members > should be the same as other online members. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (GEODE-9060) checkMyStateOnMemebers is better not to change the replicates
[ https://issues.apache.org/jira/browse/GEODE-9060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaojian Zhou resolved GEODE-9060. -- Fix Version/s: 1.12.8 1.13.7 1.14.3 Resolution: Fixed > checkMyStateOnMemebers is better not to change the replicates > - > > Key: GEODE-9060 > URL: https://issues.apache.org/jira/browse/GEODE-9060 > Project: Geode > Issue Type: Bug >Reporter: Xiaojian Zhou >Assignee: Xiaojian Zhou >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > Fix For: 1.12.8, 1.13.7, 1.14.3, 1.15.0 > > > This is an enhancement to previous GEODE-9003. > The previous fix will remove the members in replicates if it cannot recognize > current member, thus these removed members will not acting as GII provider > candidates. The fix is correct. > However, Dan suggested to keep the replicates as is to be more conservative. > These members will still act as GII provider candidates even they cannot > recognize current member due to the split-brain. Conceptually these members > should be the same as other online members. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9060) checkMyStateOnMemebers is better not to change the replicates
[ https://issues.apache.org/jira/browse/GEODE-9060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468277#comment-17468277 ] ASF subversion and git services commented on GEODE-9060: Commit 589fc30df36c5c0f4eeb6edf80dd105c4ac43540 in geode's branch refs/heads/support/1.13 from Xiaojian Zhou [ https://gitbox.apache.org/repos/asf?p=geode.git;h=589fc30 ] GEODE-9060: Remove the member from a copy of replicates as GII candid… (#6246) * GEODE-9060: Remove the member from a copy of replicates as GII candidate if it's not part of the same distributed system, but leave original replicates unchanged. (cherry picked from commit 76a5afddc9eaecea9f0b4528a910eb6761e1a3a1) > checkMyStateOnMemebers is better not to change the replicates > - > > Key: GEODE-9060 > URL: https://issues.apache.org/jira/browse/GEODE-9060 > Project: Geode > Issue Type: Bug >Reporter: Xiaojian Zhou >Assignee: Xiaojian Zhou >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > Fix For: 1.15.0 > > > This is an enhancement to previous GEODE-9003. > The previous fix will remove the members in replicates if it cannot recognize > current member, thus these removed members will not acting as GII provider > candidates. The fix is correct. > However, Dan suggested to keep the replicates as is to be more conservative. > These members will still act as GII provider candidates even they cannot > recognize current member due to the split-brain. Conceptually these members > should be the same as other online members. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-8644) SerialGatewaySenderQueueDUnitTest.unprocessedTokensMapShouldDrainCompletely() intermittently fails when queues drain too slowly
[ https://issues.apache.org/jira/browse/GEODE-8644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468276#comment-17468276 ] ASF subversion and git services commented on GEODE-8644: Commit d974f151ce5dc03160410c79a17d549235981e95 in geode's branch refs/heads/develop from Xiaojian Zhou [ https://gitbox.apache.org/repos/asf?p=geode.git;h=d974f15 ] GEODE-8644: CME will send additional UPDATE_VERSION event via serial … (#7204) co-authored-by: mhansonp > SerialGatewaySenderQueueDUnitTest.unprocessedTokensMapShouldDrainCompletely() > intermittently fails when queues drain too slowly > --- > > Key: GEODE-8644 > URL: https://issues.apache.org/jira/browse/GEODE-8644 > Project: Geode > Issue Type: Bug >Affects Versions: 1.15.0 >Reporter: Benjamin P Ross >Assignee: Xiaojian Zhou >Priority: Major > Labels: GeodeOperationAPI, needsTriage, pull-request-available > > Currently the test > SerialGatewaySenderQueueDUnitTest.unprocessedTokensMapShouldDrainCompletely() > relies on a 2 second delay to allow for queues to finish draining after > finishing the put operation. If queues take longer than 2 seconds to drain > the test will fail. We should change the test to wait for the queues to be > empty with a long timeout in case the queues never fully drain. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9060) checkMyStateOnMemebers is better not to change the replicates
[ https://issues.apache.org/jira/browse/GEODE-9060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468273#comment-17468273 ] ASF subversion and git services commented on GEODE-9060: Commit c9bb7644f210ed6d5a1f35de7dca45659e904a3c in geode's branch refs/heads/support/1.14 from Xiaojian Zhou [ https://gitbox.apache.org/repos/asf?p=geode.git;h=c9bb764 ] GEODE-9060: Remove the member from a copy of replicates as GII candid… (#6246) (#7230) * GEODE-9060: Remove the member from a copy of replicates as GII candidate if it's not part of the same distributed system, but leave original replicates unchanged. (cherry picked from commit 76a5afddc9eaecea9f0b4528a910eb6761e1a3a1) > checkMyStateOnMemebers is better not to change the replicates > - > > Key: GEODE-9060 > URL: https://issues.apache.org/jira/browse/GEODE-9060 > Project: Geode > Issue Type: Bug >Reporter: Xiaojian Zhou >Assignee: Xiaojian Zhou >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > Fix For: 1.15.0 > > > This is an enhancement to previous GEODE-9003. > The previous fix will remove the members in replicates if it cannot recognize > current member, thus these removed members will not acting as GII provider > candidates. The fix is correct. > However, Dan suggested to keep the replicates as is to be more conservative. > These members will still act as GII provider candidates even they cannot > recognize current member due to the split-brain. Conceptually these members > should be the same as other online members. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-9918) Distributed transaction is not a supported feature in geode
Eric Shu created GEODE-9918: --- Summary: Distributed transaction is not a supported feature in geode Key: GEODE-9918 URL: https://issues.apache.org/jira/browse/GEODE-9918 Project: Geode Issue Type: Bug Components: transactions Reporter: Eric Shu Geode should throw UnsupportedOperationException when CacheTransactionManager.setDistributed(true) is invoked. As the feature is currently not supported. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-9918) Distributed transaction is not a supported feature in geode
[ https://issues.apache.org/jira/browse/GEODE-9918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-9918: Labels: GeodeOperationAPI (was: ) > Distributed transaction is not a supported feature in geode > --- > > Key: GEODE-9918 > URL: https://issues.apache.org/jira/browse/GEODE-9918 > Project: Geode > Issue Type: Bug > Components: transactions >Reporter: Eric Shu >Priority: Major > Labels: GeodeOperationAPI > > Geode should throw UnsupportedOperationException when > CacheTransactionManager.setDistributed(true) is invoked. As the feature is > currently not supported. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-9917) CI Failure: (Windows) ManagementAdapterTest > testHandlingNotificationsConcurrently
Ray Ingles created GEODE-9917:
-
Summary: CI Failure: (Windows) ManagementAdapterTest >
testHandlingNotificationsConcurrently
Key: GEODE-9917
URL: https://issues.apache.org/jira/browse/GEODE-9917
Project: Geode
Issue Type: Bug
Components: management
Affects Versions: 1.15.0
Reporter: Ray Ingles
{{> Task :geode-core:integrationTest
ManagementAdapterTest > testHandlingNotificationsConcurrently FAILED
java.lang.RuntimeException: java.util.concurrent.TimeoutException
at
org.apache.geode.test.junit.rules.ConcurrencyRule$ProtectedErrorCollector.verify(ConcurrencyRule.java:489)
at
org.apache.geode.test.junit.rules.ConcurrencyRule.executeInParallel(ConcurrencyRule.java:154)
at
org.apache.geode.management.internal.beans.ManagementAdapterTest.testHandlingNotificationsConcurrently(ManagementAdapterTest.java:122)
Caused by:
java.util.concurrent.TimeoutException
at java.util.concurrent.FutureTask.get(FutureTask.java:204)
at
org.apache.geode.test.junit.rules.ConcurrencyRule.awaitFuture(ConcurrencyRule.java:227)
at
org.apache.geode.test.junit.rules.ConcurrencyRule.awaitFutures(ConcurrencyRule.java:219)
at
org.apache.geode.test.junit.rules.ConcurrencyRule.executeInParallel(ConcurrencyRule.java:153)
... 1 more}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9917) CI Failure: (Windows) ManagementAdapterTest > testHandlingNotificationsConcurrently
[
https://issues.apache.org/jira/browse/GEODE-9917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468269#comment-17468269
]
Geode Integration commented on GEODE-9917:
--
Seen in [windows-core-integration-test-openjdk11
#68|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/windows-core-integration-test-openjdk11/builds/68]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0754/test-results/integrationTest/1641098093/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0754/test-artifacts/1641098093/windows-coreintegrationtestfiles-openjdk11-1.15.0-build.0754.tgz].
> CI Failure: (Windows) ManagementAdapterTest >
> testHandlingNotificationsConcurrently
> ---
>
> Key: GEODE-9917
> URL: https://issues.apache.org/jira/browse/GEODE-9917
> Project: Geode
> Issue Type: Bug
> Components: management
>Affects Versions: 1.15.0
>Reporter: Ray Ingles
>Priority: Major
>
> {{> Task :geode-core:integrationTest
> ManagementAdapterTest > testHandlingNotificationsConcurrently FAILED
> java.lang.RuntimeException: java.util.concurrent.TimeoutException
> at
> org.apache.geode.test.junit.rules.ConcurrencyRule$ProtectedErrorCollector.verify(ConcurrencyRule.java:489)
> at
> org.apache.geode.test.junit.rules.ConcurrencyRule.executeInParallel(ConcurrencyRule.java:154)
> at
> org.apache.geode.management.internal.beans.ManagementAdapterTest.testHandlingNotificationsConcurrently(ManagementAdapterTest.java:122)
> Caused by:
> java.util.concurrent.TimeoutException
> at java.util.concurrent.FutureTask.get(FutureTask.java:204)
> at
> org.apache.geode.test.junit.rules.ConcurrencyRule.awaitFuture(ConcurrencyRule.java:227)
> at
> org.apache.geode.test.junit.rules.ConcurrencyRule.awaitFutures(ConcurrencyRule.java:219)
> at
> org.apache.geode.test.junit.rules.ConcurrencyRule.executeInParallel(ConcurrencyRule.java:153)
> ... 1 more}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9916) CI Failure: RestAPIOnRegionFunctionExecutionDUnitTest > testOnRegionExecutionWithPartitionRegion
[
https://issues.apache.org/jira/browse/GEODE-9916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468246#comment-17468246
]
Geode Integration commented on GEODE-9916:
--
Seen in [distributed-test-openjdk8
#598|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/598]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0753/test-results/distributedTest/1641099877/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0753/test-artifacts/1641099877/distributedtestfiles-openjdk8-1.15.0-build.0753.tgz].
> CI Failure: RestAPIOnRegionFunctionExecutionDUnitTest >
> testOnRegionExecutionWithPartitionRegion
>
>
> Key: GEODE-9916
> URL: https://issues.apache.org/jira/browse/GEODE-9916
> Project: Geode
> Issue Type: Bug
> Components: rest (dev)
>Affects Versions: 1.15.0
>Reporter: Ray Ingles
>Priority: Major
>
> See related test artifacts.
> {{RestAPIOnRegionFunctionExecutionDUnitTest >
> testOnRegionExecutionWithPartitionRegion[1] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.test.dunit.internal.IdentifiableCallable.call in VM 0
> running on Host
> heavy-lifter-ffd951ad-1cd6-50b7-9fe2-e85ab1050b68.c.apachegeode-ci.internal
> with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:461)
> at
> org.apache.geode.rest.internal.web.controllers.RestAPIOnRegionFunctionExecutionDUnitTest.createCacheAndRegisterFunction(RestAPIOnRegionFunctionExecutionDUnitTest.java:135)
> at
> org.apache.geode.rest.internal.web.controllers.RestAPIOnRegionFunctionExecutionDUnitTest.testOnRegionExecutionWithPartitionRegion(RestAPIOnRegionFunctionExecutionDUnitTest.java:178)
> Caused by:
> java.lang.IllegalStateException: A connection to a distributed system
> already exists in this VM. It has the following configuration:
> ack-severe-alert-threshold="0"}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (GEODE-9916) CI Failure: RestAPIOnRegionFunctionExecutionDUnitTest > testOnRegionExecutionWithPartitionRegion
Ray Ingles created GEODE-9916:
-
Summary: CI Failure: RestAPIOnRegionFunctionExecutionDUnitTest >
testOnRegionExecutionWithPartitionRegion
Key: GEODE-9916
URL: https://issues.apache.org/jira/browse/GEODE-9916
Project: Geode
Issue Type: Bug
Components: rest (dev)
Affects Versions: 1.15.0
Reporter: Ray Ingles
See related test artifacts.
{{RestAPIOnRegionFunctionExecutionDUnitTest >
testOnRegionExecutionWithPartitionRegion[1] FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.test.dunit.internal.IdentifiableCallable.call in VM 0 running
on Host
heavy-lifter-ffd951ad-1cd6-50b7-9fe2-e85ab1050b68.c.apachegeode-ci.internal
with 4 VMs
at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
at org.apache.geode.test.dunit.VM.invoke(VM.java:461)
at
org.apache.geode.rest.internal.web.controllers.RestAPIOnRegionFunctionExecutionDUnitTest.createCacheAndRegisterFunction(RestAPIOnRegionFunctionExecutionDUnitTest.java:135)
at
org.apache.geode.rest.internal.web.controllers.RestAPIOnRegionFunctionExecutionDUnitTest.testOnRegionExecutionWithPartitionRegion(RestAPIOnRegionFunctionExecutionDUnitTest.java:178)
Caused by:
java.lang.IllegalStateException: A connection to a distributed system
already exists in this VM. It has the following configuration:
ack-severe-alert-threshold="0"}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (GEODE-9915) CI Failure: PersistentPartitionedRegionDistributedTest > testCacheCloseDuringBucketMoveDoesntCauseDataLoss
Ray Ingles created GEODE-9915: - Summary: CI Failure: PersistentPartitionedRegionDistributedTest > testCacheCloseDuringBucketMoveDoesntCauseDataLoss Key: GEODE-9915 URL: https://issues.apache.org/jira/browse/GEODE-9915 Project: Geode Issue Type: Bug Components: tests Reporter: Ray Ingles NPE during execution, see linked test artifacts. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9915) CI Failure: PersistentPartitionedRegionDistributedTest > testCacheCloseDuringBucketMoveDoesntCauseDataLoss
[ https://issues.apache.org/jira/browse/GEODE-9915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468242#comment-17468242 ] Geode Integration commented on GEODE-9915: -- Seen in [distributed-test-openjdk8 #579|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/579] ... see [test results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0753/test-results/distributedTest/1641083901/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0753/test-artifacts/1641083901/distributedtestfiles-openjdk8-1.15.0-build.0753.tgz]. > CI Failure: PersistentPartitionedRegionDistributedTest > > testCacheCloseDuringBucketMoveDoesntCauseDataLoss > -- > > Key: GEODE-9915 > URL: https://issues.apache.org/jira/browse/GEODE-9915 > Project: Geode > Issue Type: Bug > Components: tests >Reporter: Ray Ingles >Priority: Major > > NPE during execution, see linked test artifacts. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-8658) CI failure: LauncherMemberMXBeanIntegrationTest.showOSMetrics_reconstructsOSMetricsFromCompositeDataType
[
https://issues.apache.org/jira/browse/GEODE-8658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468235#comment-17468235
]
Geode Integration commented on GEODE-8658:
--
Seen on support/1.12 in [windows-core-integration-test-openjdk8
#16|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/windows-core-integration-test-openjdk8/builds/16]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.8-build.0326/test-results/integrationTest/1641107850/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.8-build.0326/test-artifacts/1641107850/windows-coreintegrationtestfiles-openjdk8-1.12.8-build.0326.tgz].
> CI failure:
> LauncherMemberMXBeanIntegrationTest.showOSMetrics_reconstructsOSMetricsFromCompositeDataType
>
>
> Key: GEODE-8658
> URL: https://issues.apache.org/jira/browse/GEODE-8658
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Kirk Lund
>Assignee: Jens Deppe
>Priority: Major
>
> This appears to be an intermittent failure on Windows
> (WindowsCoreIntegrationTestOpenJDK11):
> {noformat}
> java.lang.AssertionError:
> Expecting:
> <(1082576896,1082818560)>
> to match 'committed virtual memory size]' predicate.
> at
> org.apache.geode.distributed.LauncherMemberMXBeanIntegrationTest.showOSMetrics_reconstructsOSMetricsFromCompositeDataType(LauncherMemberMXBeanIntegrationTest.java:128)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
> 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:54)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:61)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at
> org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
> at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
> at
> org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:62)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
>
[jira] [Updated] (GEODE-9354) Refactor ArgumentRedactor and add tests for ssl-*store-password props
[
https://issues.apache.org/jira/browse/GEODE-9354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-9354:
-
Priority: Minor (was: Major)
> Refactor ArgumentRedactor and add tests for ssl-*store-password props
> -
>
> Key: GEODE-9354
> URL: https://issues.apache.org/jira/browse/GEODE-9354
> Project: Geode
> Issue Type: Bug
> Components: logging
>Affects Versions: 1.12.4, 1.13.4
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Minor
> Labels: GeodeOperationAPI, pull-request-available
> Fix For: 1.12.5, 1.13.5, 1.14.0, 1.15.0
>
>
> Refactor ArgumentRedactor to clean it up and make sure it's efficient.
> Add test coverage for log statements containing:
> {noformat}
> -Dgemfire.ssl-truststore-password=
> -Dgemfire.ssl-keystore-password=
> {noformat}
> Related to
> [CVE-2021-34797|https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-34797]
> in which logging is vulnerable to a log file redaction of sensitive
> information flaw when using values that begin with characters other than
> letters or numbers for passwords and security properties with the prefix
> "sysprop-", "javax.net.ssl", or "security-". This issue is fixed by
> overhauling the log file redaction in Apache Geode versions 1.12.5, 1.13.5,
> and 1.14.0.
> Fixed in https://github.com/apache/geode/pull/6641.
> Backported to:
> * 1.14 in https://github.com/apache/geode/pull/6747
> * 1.13 in https://github.com/apache/geode/pull/6749
> * 1.12 in https://github.com/apache/geode/pull/6750
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-7098) Tomcat8SessionsClientServerDUnitTest fails with ConnectException
[ https://issues.apache.org/jira/browse/GEODE-7098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468234#comment-17468234 ] Geode Integration commented on GEODE-7098: -- Seen on support/1.12 in [distributed-test-openjdk8 #18|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/distributed-test-openjdk8/builds/18] ... see [test results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.8-build.0326/test-results/distributedTest/1641034666/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.8-build.0326/test-artifacts/1641034666/distributedtestfiles-openjdk8-1.12.8-build.0326.tgz]. > Tomcat8SessionsClientServerDUnitTest fails with ConnectException > > > Key: GEODE-7098 > URL: https://issues.apache.org/jira/browse/GEODE-7098 > Project: Geode > Issue Type: Bug >Affects Versions: 1.11.0 >Reporter: Benjamin P Ross >Assignee: Mark Hanson >Priority: Major > Labels: flaky > Fix For: 1.13.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > We've seen Tomcat8SessionsClientServerDUnitTest.testExtraSessionsNotCreated > fail with > a ConnectException > org.apache.geode.modules.session.Tomcat8SessionsClientServerDUnitTest > > testExtraSessionsNotCreated FAILED > java.net.ConnectException: Connection refused (Connection refused) > Caused by: > java.net.ConnectException: Connection refused (Connection refused) > This could be an environmental error, but if a pattern develops it could be > due to a flaky test. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-9354) Refactor ArgumentRedactor and add tests for ssl-*store-password props
[
https://issues.apache.org/jira/browse/GEODE-9354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-9354:
-
Description:
Refactor ArgumentRedactor to clean it up and make sure it's efficient.
Add test coverage for log statements containing:
{noformat}
-Dgemfire.ssl-truststore-password=
-Dgemfire.ssl-keystore-password=
{noformat}
Related to
[CVE-2021-34797|https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-34797]
in which logging is vulnerable to a log file redaction of sensitive information
flaw when using values that begin with characters other than letters or numbers
for passwords and security properties with the prefix "sysprop-",
"javax.net.ssl", or "security-". This issue is fixed by overhauling the log
file redaction in Apache Geode versions 1.12.5, 1.13.5, and 1.14.0.
Fixed in https://github.com/apache/geode/pull/6641.
Backported to:
* 1.14 in https://github.com/apache/geode/pull/6747
* 1.13 in https://github.com/apache/geode/pull/6749
* 1.12 in https://github.com/apache/geode/pull/6750
was:
Refactor ArgumentRedactor to clean it up and make sure it's efficient.
Add test coverage for log statements containing:
{noformat}
-Dgemfire.ssl-truststore-password=
-Dgemfire.ssl-keystore-password=
{noformat}
Related to
[CVE-2021-34797|https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-34797]
in which logging is vulnerable to a log file redaction of sensitive information
flaw when using values that begin with characters other than letters or numbers
for passwords and security properties with the prefix "sysprop-",
"javax.net.ssl", or "security-".
Fixed in https://github.com/apache/geode/pull/6641.
Backported to:
* 1.14 in https://github.com/apache/geode/pull/6747
* 1.13 in https://github.com/apache/geode/pull/6749
* 1.12 in https://github.com/apache/geode/pull/6750
> Refactor ArgumentRedactor and add tests for ssl-*store-password props
> -
>
> Key: GEODE-9354
> URL: https://issues.apache.org/jira/browse/GEODE-9354
> Project: Geode
> Issue Type: Bug
> Components: logging
>Affects Versions: 1.12.4, 1.13.4
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
> Fix For: 1.12.5, 1.13.5, 1.14.0, 1.15.0
>
>
> Refactor ArgumentRedactor to clean it up and make sure it's efficient.
> Add test coverage for log statements containing:
> {noformat}
> -Dgemfire.ssl-truststore-password=
> -Dgemfire.ssl-keystore-password=
> {noformat}
> Related to
> [CVE-2021-34797|https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-34797]
> in which logging is vulnerable to a log file redaction of sensitive
> information flaw when using values that begin with characters other than
> letters or numbers for passwords and security properties with the prefix
> "sysprop-", "javax.net.ssl", or "security-". This issue is fixed by
> overhauling the log file redaction in Apache Geode versions 1.12.5, 1.13.5,
> and 1.14.0.
> Fixed in https://github.com/apache/geode/pull/6641.
> Backported to:
> * 1.14 in https://github.com/apache/geode/pull/6747
> * 1.13 in https://github.com/apache/geode/pull/6749
> * 1.12 in https://github.com/apache/geode/pull/6750
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9354) Refactor ArgumentRedactor and add tests for ssl-*store-password props
[
https://issues.apache.org/jira/browse/GEODE-9354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-9354:
-
Description:
Refactor ArgumentRedactor to clean it up and make sure it's efficient.
Add test coverage for log statements containing:
{noformat}
-Dgemfire.ssl-truststore-password=
-Dgemfire.ssl-keystore-password=
{noformat}
Related to
[CVE-2021-34797|https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-34797]
in which logging is vulnerable to a log file redaction of sensitive information
flaw when using values that begin with characters other than letters or numbers
for passwords and security properties with the prefix "sysprop-",
"javax.net.ssl", or "security-".
Fixed in https://github.com/apache/geode/pull/6641.
Backported to:
* 1.14 in https://github.com/apache/geode/pull/6747
* 1.13 in https://github.com/apache/geode/pull/6749
* 1.12 in https://github.com/apache/geode/pull/6750
was:
Refactor ArgumentRedactor to clean it up and make sure it's efficient.
Add test coverage for log statements containing:
{noformat}
-Dgemfire.ssl-truststore-password=
-Dgemfire.ssl-keystore-password=
{noformat}
Related to
[CVE-2021-34797|https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-34797]
in which logging is vulnerable to a log file redaction of sensitive information
flaw when using values that begin with characters other than letters or numbers
for passwords and security properties with the prefix "sysprop-",
"javax.net.ssl", or "security-".
Fixed in https://github.com/apache/geode/pull/6641.
Backported to:
* 1.14 in https://github.com/apache/geode/pull/6747
> Refactor ArgumentRedactor and add tests for ssl-*store-password props
> -
>
> Key: GEODE-9354
> URL: https://issues.apache.org/jira/browse/GEODE-9354
> Project: Geode
> Issue Type: Bug
> Components: logging
>Affects Versions: 1.12.4, 1.13.4
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
> Fix For: 1.12.5, 1.13.5, 1.14.0, 1.15.0
>
>
> Refactor ArgumentRedactor to clean it up and make sure it's efficient.
> Add test coverage for log statements containing:
> {noformat}
> -Dgemfire.ssl-truststore-password=
> -Dgemfire.ssl-keystore-password=
> {noformat}
> Related to
> [CVE-2021-34797|https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-34797]
> in which logging is vulnerable to a log file redaction of sensitive
> information flaw when using values that begin with characters other than
> letters or numbers for passwords and security properties with the prefix
> "sysprop-", "javax.net.ssl", or "security-".
> Fixed in https://github.com/apache/geode/pull/6641.
> Backported to:
> * 1.14 in https://github.com/apache/geode/pull/6747
> * 1.13 in https://github.com/apache/geode/pull/6749
> * 1.12 in https://github.com/apache/geode/pull/6750
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9354) Refactor ArgumentRedactor and add tests for ssl-*store-password props
[
https://issues.apache.org/jira/browse/GEODE-9354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-9354:
-
Description:
Refactor ArgumentRedactor to clean it up and make sure it's efficient.
Add test coverage for log statements containing:
{noformat}
-Dgemfire.ssl-truststore-password=
-Dgemfire.ssl-keystore-password=
{noformat}
Related to
[CVE-2021-34797|https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-34797]
in which logging is vulnerable to a log file redaction of sensitive information
flaw when using values that begin with characters other than letters or numbers
for passwords and security properties with the prefix "sysprop-",
"javax.net.ssl", or "security-".
Fixed in https://github.com/apache/geode/pull/6641.
Backported to:
* 1.14 in https://github.com/apache/geode/pull/6747
was:
Refactor ArgumentRedactor to clean it up and make sure it's efficient.
Add test coverage for log statements containing:
{noformat}
-Dgemfire.ssl-truststore-password=
-Dgemfire.ssl-keystore-password=
{noformat}
Related to
[CVE-2021-34797|https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-34797]
in which logging is vulnerable to a log file redaction of sensitive information
flaw when using values that begin with characters other than letters or numbers
for passwords and security properties with the prefix "sysprop-",
"javax.net.ssl", or "security-".
Fixed in https://github.com/apache/geode/pull/6641.
Backported to 1.12 in
> Refactor ArgumentRedactor and add tests for ssl-*store-password props
> -
>
> Key: GEODE-9354
> URL: https://issues.apache.org/jira/browse/GEODE-9354
> Project: Geode
> Issue Type: Bug
> Components: logging
>Affects Versions: 1.12.4, 1.13.4
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
> Fix For: 1.12.5, 1.13.5, 1.14.0, 1.15.0
>
>
> Refactor ArgumentRedactor to clean it up and make sure it's efficient.
> Add test coverage for log statements containing:
> {noformat}
> -Dgemfire.ssl-truststore-password=
> -Dgemfire.ssl-keystore-password=
> {noformat}
> Related to
> [CVE-2021-34797|https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-34797]
> in which logging is vulnerable to a log file redaction of sensitive
> information flaw when using values that begin with characters other than
> letters or numbers for passwords and security properties with the prefix
> "sysprop-", "javax.net.ssl", or "security-".
> Fixed in https://github.com/apache/geode/pull/6641.
> Backported to:
> * 1.14 in https://github.com/apache/geode/pull/6747
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9354) Refactor ArgumentRedactor and add tests for ssl-*store-password props
[
https://issues.apache.org/jira/browse/GEODE-9354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-9354:
-
Description:
Refactor ArgumentRedactor to clean it up and make sure it's efficient.
Add test coverage for log statements containing:
{noformat}
-Dgemfire.ssl-truststore-password=
-Dgemfire.ssl-keystore-password=
{noformat}
Related to
[CVE-2021-34797|https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-34797]
in which logging is vulnerable to a log file redaction of sensitive information
flaw when using values that begin with characters other than letters or numbers
for passwords and security properties with the prefix "sysprop-",
"javax.net.ssl", or "security-".
Fixed in https://github.com/apache/geode/pull/6641.
Backported to 1.12 in
was:
Refactor ArgumentRedactor to clean it up and make sure it's efficient.
Add test coverage for log statements containing:
{noformat}
-Dgemfire.ssl-truststore-password=
-Dgemfire.ssl-keystore-password=
{noformat}
Related to
[CVE-2021-34797|https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-34797]
in which logging is vulnerable to a log file redaction of sensitive information
flaw when using values that begin with characters other than letters or numbers
for passwords and security properties with the prefix "sysprop-",
"javax.net.ssl", or "security-".
Fixed in https://github.com/apache/geode/pull/6641.
> Refactor ArgumentRedactor and add tests for ssl-*store-password props
> -
>
> Key: GEODE-9354
> URL: https://issues.apache.org/jira/browse/GEODE-9354
> Project: Geode
> Issue Type: Bug
> Components: logging
>Affects Versions: 1.12.4, 1.13.4
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
> Fix For: 1.12.5, 1.13.5, 1.14.0, 1.15.0
>
>
> Refactor ArgumentRedactor to clean it up and make sure it's efficient.
> Add test coverage for log statements containing:
> {noformat}
> -Dgemfire.ssl-truststore-password=
> -Dgemfire.ssl-keystore-password=
> {noformat}
> Related to
> [CVE-2021-34797|https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-34797]
> in which logging is vulnerable to a log file redaction of sensitive
> information flaw when using values that begin with characters other than
> letters or numbers for passwords and security properties with the prefix
> "sysprop-", "javax.net.ssl", or "security-".
> Fixed in https://github.com/apache/geode/pull/6641.
> Backported to 1.12 in
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9914) CI Failures: JmxServerReconnectDistributedTest
[ https://issues.apache.org/jira/browse/GEODE-9914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468231#comment-17468231 ] Geode Integration commented on GEODE-9914: -- Seen in [distributed-test-openjdk8 #552|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/552] ... see [test results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0753/test-results/distributedTest/1641065590/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0753/test-artifacts/1641065590/distributedtestfiles-openjdk8-1.15.0-build.0753.tgz]. > CI Failures: JmxServerReconnectDistributedTest > -- > > Key: GEODE-9914 > URL: https://issues.apache.org/jira/browse/GEODE-9914 > Project: Geode > Issue Type: Bug > Components: jmx >Affects Versions: 1.13.0, 1.14.0, 1.15.0 >Reporter: Ray Ingles >Priority: Major > > Multiple failures in the latest regression in different places. Possibly > related to bumping versions of dependencies due to Log4j bug fixes? -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9914) CI Failures: JmxServerReconnectDistributedTest
[ https://issues.apache.org/jira/browse/GEODE-9914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468228#comment-17468228 ] Geode Integration commented on GEODE-9914: -- Seen on support/1.13 in [distributed-test-openjdk8 #16|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-main/jobs/distributed-test-openjdk8/builds/16] ... see [test results|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.7-build.0632/test-results/distributedTest/1640823541/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.7-build.0632/test-artifacts/1640823541/distributedtestfiles-openjdk8-1.13.7-build.0632.tgz]. > CI Failures: JmxServerReconnectDistributedTest > -- > > Key: GEODE-9914 > URL: https://issues.apache.org/jira/browse/GEODE-9914 > Project: Geode > Issue Type: Bug > Components: jmx >Affects Versions: 1.13.0, 1.14.0, 1.15.0 >Reporter: Ray Ingles >Priority: Major > > Multiple failures in the latest regression in different places. Possibly > related to bumping versions of dependencies due to Log4j bug fixes? -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9914) CI Failures: JmxServerReconnectDistributedTest
[ https://issues.apache.org/jira/browse/GEODE-9914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468227#comment-17468227 ] Geode Integration commented on GEODE-9914: -- Seen on support/1.13 in [distributed-test-openjdk8 #17|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-main/jobs/distributed-test-openjdk8/builds/17] ... see [test results|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.7-build.0632/test-results/distributedTest/1640838918/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.7-build.0632/test-artifacts/1640838918/distributedtestfiles-openjdk8-1.13.7-build.0632.tgz]. > CI Failures: JmxServerReconnectDistributedTest > -- > > Key: GEODE-9914 > URL: https://issues.apache.org/jira/browse/GEODE-9914 > Project: Geode > Issue Type: Bug > Components: jmx >Affects Versions: 1.13.0, 1.14.0, 1.15.0 >Reporter: Ray Ingles >Priority: Major > > Multiple failures in the latest regression in different places. Possibly > related to bumping versions of dependencies due to Log4j bug fixes? -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9914) CI Failures: JmxServerReconnectDistributedTest
[ https://issues.apache.org/jira/browse/GEODE-9914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468229#comment-17468229 ] Geode Integration commented on GEODE-9914: -- Seen in [distributed-test-openjdk8 #577|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/577] ... see [test results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0753/test-results/distributedTest/1641083399/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0753/test-artifacts/1641083399/distributedtestfiles-openjdk8-1.15.0-build.0753.tgz]. > CI Failures: JmxServerReconnectDistributedTest > -- > > Key: GEODE-9914 > URL: https://issues.apache.org/jira/browse/GEODE-9914 > Project: Geode > Issue Type: Bug > Components: jmx >Affects Versions: 1.13.0, 1.14.0, 1.15.0 >Reporter: Ray Ingles >Priority: Major > > Multiple failures in the latest regression in different places. Possibly > related to bumping versions of dependencies due to Log4j bug fixes? -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9914) CI Failures: JmxServerReconnectDistributedTest
[ https://issues.apache.org/jira/browse/GEODE-9914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468230#comment-17468230 ] Geode Integration commented on GEODE-9914: -- Seen in [distributed-test-openjdk8 #531|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/531] ... see [test results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0753/test-results/distributedTest/1641050887/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0753/test-artifacts/1641050887/distributedtestfiles-openjdk8-1.15.0-build.0753.tgz]. > CI Failures: JmxServerReconnectDistributedTest > -- > > Key: GEODE-9914 > URL: https://issues.apache.org/jira/browse/GEODE-9914 > Project: Geode > Issue Type: Bug > Components: jmx >Affects Versions: 1.13.0, 1.14.0, 1.15.0 >Reporter: Ray Ingles >Priority: Major > > Multiple failures in the latest regression in different places. Possibly > related to bumping versions of dependencies due to Log4j bug fixes? -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-9914) CI Failures: JmxServerReconnectDistributedTest
Ray Ingles created GEODE-9914: - Summary: CI Failures: JmxServerReconnectDistributedTest Key: GEODE-9914 URL: https://issues.apache.org/jira/browse/GEODE-9914 Project: Geode Issue Type: Bug Components: jmx Affects Versions: 1.14.0, 1.13.0, 1.15.0 Reporter: Ray Ingles Multiple failures in the latest regression in different places. Possibly related to bumping versions of dependencies due to Log4j bug fixes? -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9914) CI Failures: JmxServerReconnectDistributedTest
[ https://issues.apache.org/jira/browse/GEODE-9914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468226#comment-17468226 ] Geode Integration commented on GEODE-9914: -- Seen on support/1.14 in [distributed-test-openjdk8 #15|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/distributed-test-openjdk8/builds/15] ... see [test results|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.3-build.0902/test-results/distributedTest/1640863679/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.3-build.0902/test-artifacts/1640863679/distributedtestfiles-openjdk8-1.14.3-build.0902.tgz]. > CI Failures: JmxServerReconnectDistributedTest > -- > > Key: GEODE-9914 > URL: https://issues.apache.org/jira/browse/GEODE-9914 > Project: Geode > Issue Type: Bug > Components: jmx >Affects Versions: 1.13.0, 1.14.0, 1.15.0 >Reporter: Ray Ingles >Priority: Major > > Multiple failures in the latest regression in different places. Possibly > related to bumping versions of dependencies due to Log4j bug fixes? -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (GEODE-9913) A retried event can fail if the original event is still being processed and a new event for that same key occurs at the same time
Barrett Oglesby created GEODE-9913: -- Summary: A retried event can fail if the original event is still being processed and a new event for that same key occurs at the same time Key: GEODE-9913 URL: https://issues.apache.org/jira/browse/GEODE-9913 Project: Geode Issue Type: Bug Components: client/server Reporter: Barrett Oglesby -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9913) A retried event can fail if the original event is still being processed and a new event for that same key occurs at the same time
[ https://issues.apache.org/jira/browse/GEODE-9913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barrett Oglesby reassigned GEODE-9913: -- Assignee: Barrett Oglesby > A retried event can fail if the original event is still being processed and a > new event for that same key occurs at the same time > - > > Key: GEODE-9913 > URL: https://issues.apache.org/jira/browse/GEODE-9913 > Project: Geode > Issue Type: Bug > Components: client/server >Reporter: Barrett Oglesby >Assignee: Barrett Oglesby >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-9354) Refactor ArgumentRedactor and add tests for ssl-*store-password props
[
https://issues.apache.org/jira/browse/GEODE-9354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-9354:
-
Description:
Refactor ArgumentRedactor to clean it up and make sure it's efficient.
Add test coverage for log statements containing:
{noformat}
-Dgemfire.ssl-truststore-password=
-Dgemfire.ssl-keystore-password=
{noformat}
Related to
[CVE-2021-34797|https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-34797]
in which logging is vulnerable to a log file redaction of sensitive information
flaw when using values that begin with characters other than letters or numbers
for passwords and security properties with the prefix "sysprop-",
"javax.net.ssl", or "security-".
Fixed in https://github.com/apache/geode/pull/6641.
was:
Refactor ArgumentRedactor to clean it up and make sure it's efficient.
Add test coverage for log statements containing:
{noformat}
-Dgemfire.ssl-truststore-password=
-Dgemfire.ssl-keystore-password=
{noformat}
Related to
[CVE-2021-34797|https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-34797]
in which logging is vulnerable to a log file redaction of sensitive information
flaw when using values that begin with characters other than letters or numbers
for passwords and security properties with the prefix "sysprop-",
"javax.net.ssl", or "security-".
> Refactor ArgumentRedactor and add tests for ssl-*store-password props
> -
>
> Key: GEODE-9354
> URL: https://issues.apache.org/jira/browse/GEODE-9354
> Project: Geode
> Issue Type: Bug
> Components: logging
>Affects Versions: 1.12.4, 1.13.4
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
> Fix For: 1.12.5, 1.13.5, 1.14.0, 1.15.0
>
>
> Refactor ArgumentRedactor to clean it up and make sure it's efficient.
> Add test coverage for log statements containing:
> {noformat}
> -Dgemfire.ssl-truststore-password=
> -Dgemfire.ssl-keystore-password=
> {noformat}
> Related to
> [CVE-2021-34797|https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-34797]
> in which logging is vulnerable to a log file redaction of sensitive
> information flaw when using values that begin with characters other than
> letters or numbers for passwords and security properties with the prefix
> "sysprop-", "javax.net.ssl", or "security-".
> Fixed in https://github.com/apache/geode/pull/6641.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9354) Refactor ArgumentRedactor and add tests for ssl-*store-password props
[
https://issues.apache.org/jira/browse/GEODE-9354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-9354:
-
Description:
Refactor ArgumentRedactor to clean it up and make sure it's efficient.
Add test coverage for log statements containing:
{noformat}
-Dgemfire.ssl-truststore-password=
-Dgemfire.ssl-keystore-password=
{noformat}
Related to
[CVE-2021-34797|https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-34797]
in which logging is vulnerable to a log file redaction of sensitive information
flaw when using values that begin with characters other than letters or numbers
for passwords and security properties with the prefix "sysprop-",
"javax.net.ssl", or "security-".
was:
Refactor ArgumentRedactor to clean it up and make sure it's efficient.
Add test coverage for log statements containing:
{noformat}
-Dgemfire.ssl-truststore-password=
-Dgemfire.ssl-keystore-password=
{noformat}
> Refactor ArgumentRedactor and add tests for ssl-*store-password props
> -
>
> Key: GEODE-9354
> URL: https://issues.apache.org/jira/browse/GEODE-9354
> Project: Geode
> Issue Type: Wish
> Components: logging
>Affects Versions: 1.12.4, 1.13.4
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
> Fix For: 1.12.5, 1.13.5, 1.14.0, 1.15.0
>
>
> Refactor ArgumentRedactor to clean it up and make sure it's efficient.
> Add test coverage for log statements containing:
> {noformat}
> -Dgemfire.ssl-truststore-password=
> -Dgemfire.ssl-keystore-password=
> {noformat}
> Related to
> [CVE-2021-34797|https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-34797]
> in which logging is vulnerable to a log file redaction of sensitive
> information flaw when using values that begin with characters other than
> letters or numbers for passwords and security properties with the prefix
> "sysprop-", "javax.net.ssl", or "security-".
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9354) Refactor ArgumentRedactor and add tests for ssl-*store-password props
[
https://issues.apache.org/jira/browse/GEODE-9354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-9354:
-
Issue Type: Bug (was: Wish)
> Refactor ArgumentRedactor and add tests for ssl-*store-password props
> -
>
> Key: GEODE-9354
> URL: https://issues.apache.org/jira/browse/GEODE-9354
> Project: Geode
> Issue Type: Bug
> Components: logging
>Affects Versions: 1.12.4, 1.13.4
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
> Fix For: 1.12.5, 1.13.5, 1.14.0, 1.15.0
>
>
> Refactor ArgumentRedactor to clean it up and make sure it's efficient.
> Add test coverage for log statements containing:
> {noformat}
> -Dgemfire.ssl-truststore-password=
> -Dgemfire.ssl-keystore-password=
> {noformat}
> Related to
> [CVE-2021-34797|https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-34797]
> in which logging is vulnerable to a log file redaction of sensitive
> information flaw when using values that begin with characters other than
> letters or numbers for passwords and security properties with the prefix
> "sysprop-", "javax.net.ssl", or "security-".
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9354) Refactor ArgumentRedactor and add tests for ssl-*store-password props
[
https://issues.apache.org/jira/browse/GEODE-9354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-9354:
-
Description:
Refactor ArgumentRedactor to clean it up and make sure it's efficient.
Add test coverage for log statements containing:
{noformat}
-Dgemfire.ssl-truststore-password=
-Dgemfire.ssl-keystore-password=
{noformat}
---
was:
Refactor ArgumentRedactor to clean it up and make sure it's efficient.
Add test coverage for log statements containing:
{noformat}
-Dgemfire.ssl-truststore-password=
-Dgemfire.ssl-keystore-password=
{noformat}
> Refactor ArgumentRedactor and add tests for ssl-*store-password props
> -
>
> Key: GEODE-9354
> URL: https://issues.apache.org/jira/browse/GEODE-9354
> Project: Geode
> Issue Type: Wish
> Components: logging
>Affects Versions: 1.12.4, 1.13.4
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
> Fix For: 1.12.5, 1.13.5, 1.14.0, 1.15.0
>
>
> Refactor ArgumentRedactor to clean it up and make sure it's efficient.
> Add test coverage for log statements containing:
> {noformat}
> -Dgemfire.ssl-truststore-password=
> -Dgemfire.ssl-keystore-password=
> {noformat}
> ---
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9354) Refactor ArgumentRedactor and add tests for ssl-*store-password props
[
https://issues.apache.org/jira/browse/GEODE-9354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-9354:
-
Description:
Refactor ArgumentRedactor to clean it up and make sure it's efficient.
Add test coverage for log statements containing:
{noformat}
-Dgemfire.ssl-truststore-password=
-Dgemfire.ssl-keystore-password=
{noformat}
was:
Refactor ArgumentRedactor to clean it up and make sure it's efficient.
Add test coverage for log statements containing:
{noformat}
-Dgemfire.ssl-truststore-password=
-Dgemfire.ssl-keystore-password=
{noformat}
---
> Refactor ArgumentRedactor and add tests for ssl-*store-password props
> -
>
> Key: GEODE-9354
> URL: https://issues.apache.org/jira/browse/GEODE-9354
> Project: Geode
> Issue Type: Wish
> Components: logging
>Affects Versions: 1.12.4, 1.13.4
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
> Fix For: 1.12.5, 1.13.5, 1.14.0, 1.15.0
>
>
> Refactor ArgumentRedactor to clean it up and make sure it's efficient.
> Add test coverage for log statements containing:
> {noformat}
> -Dgemfire.ssl-truststore-password=
> -Dgemfire.ssl-keystore-password=
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9617) CI Failure: PartitionedRegionSingleHopDUnitTest fails with ConditionTimeoutException waiting for server to bucket map size
[
https://issues.apache.org/jira/browse/GEODE-9617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468217#comment-17468217
]
Geode Integration commented on GEODE-9617:
--
Seen in [distributed-test-openjdk8
#600|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/600]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0753/test-results/distributedTest/1641102097/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0753/test-artifacts/1641102097/distributedtestfiles-openjdk8-1.15.0-build.0753.tgz].
> CI Failure: PartitionedRegionSingleHopDUnitTest fails with
> ConditionTimeoutException waiting for server to bucket map size
> --
>
> Key: GEODE-9617
> URL: https://issues.apache.org/jira/browse/GEODE-9617
> Project: Geode
> Issue Type: Bug
> Components: client/server
>Affects Versions: 1.15.0
>Reporter: Kirk Lund
>Assignee: Mark Hanson
>Priority: Major
> Labels: pull-request-available
>
> {noformat}
> org.apache.geode.internal.cache.PartitionedRegionSingleHopDUnitTest >
> testClientMetadataForPersistentPrs FAILED
> org.awaitility.core.ConditionTimeoutException: Assertion condition
> defined as a lambda expression in
> org.apache.geode.internal.cache.PartitionedRegionSingleHopDUnitTest that uses
> org.apache.geode.cache.client.internal.ClientMetadataService,
> org.apache.geode.cache.client.internal.ClientMetadataServiceorg.apache.geode.cache.Region
>
> Expecting actual not to be null within 5 minutes.
> at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:166)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:939)
> at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:723)
> at
> org.apache.geode.internal.cache.PartitionedRegionSingleHopDUnitTest.testClientMetadataForPersistentPrs(PartitionedRegionSingleHopDUnitTest.java:971)
> Caused by:
> java.lang.AssertionError:
> Expecting actual not to be null
> at
> org.apache.geode.internal.cache.PartitionedRegionSingleHopDUnitTest.lambda$testClientMetadataForPersistentPrs$26(PartitionedRegionSingleHopDUnitTest.java:976)
> {noformat}
> {noformat}
> org.apache.geode.internal.cache.PartitionedRegionSingleHopDUnitTest >
> testMetadataServiceCallAccuracy_FromGetOp FAILED
> org.awaitility.core.ConditionTimeoutException: Assertion condition
> defined as a lambda expression in
> org.apache.geode.internal.cache.PartitionedRegionSingleHopDUnitTest that uses
> org.apache.geode.cache.client.internal.ClientMetadataService
> Expecting value to be false but was true expected:<[fals]e> but
> was:<[tru]e> within 5 minutes.
> at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:166)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:939)
> at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:723)
> at
> org.apache.geode.internal.cache.PartitionedRegionSingleHopDUnitTest.testMetadataServiceCallAccuracy_FromGetOp(PartitionedRegionSingleHopDUnitTest.java:394)
> Caused by:
> org.junit.ComparisonFailure:
> Expecting value to be false but was true expected:<[fals]e> but
> was:<[tru]e>
> at sun.reflect.GeneratedConstructorAccessor29.newInstance(Unknown
> Source)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.internal.cache.PartitionedRegionSingleHopDUnitTest.lambda$testMetadataServiceCallAccuracy_FromGetOp$6(PartitionedRegionSingleHopDUnitTest.java:395)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9912) Add unique identifier to DUnit log lines
[
https://issues.apache.org/jira/browse/GEODE-9912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-9912:
--
Labels: pull-request-available (was: )
> Add unique identifier to DUnit log lines
>
>
> Key: GEODE-9912
> URL: https://issues.apache.org/jira/browse/GEODE-9912
> Project: Geode
> Issue Type: Test
> Components: tests
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
> Labels: pull-request-available
>
> Adding an arbitrary random string to DUnit log lines allows to distinguish
> individual test output for repeated tests. In such cases tests run in
> parallel and individual test log lines are interleaved making debugging very
> difficult. So log lines would look something like:
> {noformat}
> [vm0-51ec] [info 2021/12/24 15:43:54.367 UTC Connection(1)-10.138.0.70>; tid=0x1d] Reinitializing JarDeploymentService
> with new working directory: null
> [vm0-47b7] [info 2021/12/24 15:43:54.416 UTC Connection(1)-10.138.0.70> tid=0x1d] Reinitializing JarDeploymentService with
> new working directory: null
> [vm1-47b7] [info 2021/12/24 15:43:54.431 UTC Connection(1)-10.138.0.70> tid=0x1d] Received method:
> org.apache.geode.test.dunit.internal.IdentifiableCallable.call with 0 args on
> object: IdentifiableCallable(0:start locator in vm0)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (GEODE-9912) Add unique identifier to DUnit log lines
[
https://issues.apache.org/jira/browse/GEODE-9912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jens Deppe reassigned GEODE-9912:
-
Assignee: Jens Deppe
> Add unique identifier to DUnit log lines
>
>
> Key: GEODE-9912
> URL: https://issues.apache.org/jira/browse/GEODE-9912
> Project: Geode
> Issue Type: Test
> Components: tests
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
>
> Adding an arbitrary random string to DUnit log lines allows to distinguish
> individual test output for repeated tests. In such cases tests run in
> parallel and individual test log lines are interleaved making debugging very
> difficult. So log lines would look something like:
> {noformat}
> [vm0-51ec] [info 2021/12/24 15:43:54.367 UTC Connection(1)-10.138.0.70>; tid=0x1d] Reinitializing JarDeploymentService
> with new working directory: null
> [vm0-47b7] [info 2021/12/24 15:43:54.416 UTC Connection(1)-10.138.0.70> tid=0x1d] Reinitializing JarDeploymentService with
> new working directory: null
> [vm1-47b7] [info 2021/12/24 15:43:54.431 UTC Connection(1)-10.138.0.70> tid=0x1d] Received method:
> org.apache.geode.test.dunit.internal.IdentifiableCallable.call with 0 args on
> object: IdentifiableCallable(0:start locator in vm0)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (GEODE-9912) Add unique identifier to DUnit log lines
Jens Deppe created GEODE-9912:
-
Summary: Add unique identifier to DUnit log lines
Key: GEODE-9912
URL: https://issues.apache.org/jira/browse/GEODE-9912
Project: Geode
Issue Type: Test
Components: tests
Reporter: Jens Deppe
Adding an arbitrary random string to DUnit log lines allows to distinguish
individual test output for repeated tests. In such cases tests run in parallel
and individual test log lines are interleaved making debugging very difficult.
So log lines would look something like:
{noformat}
[vm0-51ec] [info 2021/12/24 15:43:54.367 UTC ; tid=0x1d] Reinitializing JarDeploymentService with
new working directory: null
[vm0-47b7] [info 2021/12/24 15:43:54.416 UTC tid=0x1d] Reinitializing JarDeploymentService with
new working directory: null
[vm1-47b7] [info 2021/12/24 15:43:54.431 UTC tid=0x1d] Received method:
org.apache.geode.test.dunit.internal.IdentifiableCallable.call with 0 args on
object: IdentifiableCallable(0:start locator in vm0)
{noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-6296) CI failure: CqResultSetUsingPoolOptimizedExecuteDUnitTest.testCqResultsCachingForMultipleCQs
[
https://issues.apache.org/jira/browse/GEODE-6296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468196#comment-17468196
]
Geode Integration commented on GEODE-6296:
--
Seen in [distributed-test-openjdk8
#581|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/581]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0753/test-results/distributedTest/1641090546/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0753/test-artifacts/1641090546/distributedtestfiles-openjdk8-1.15.0-build.0753.tgz].
> CI failure:
> CqResultSetUsingPoolOptimizedExecuteDUnitTest.testCqResultsCachingForMultipleCQs
>
>
> Key: GEODE-6296
> URL: https://issues.apache.org/jira/browse/GEODE-6296
> Project: Geode
> Issue Type: Bug
> Components: client queues
>Reporter: Bruce J Schuchardt
>Assignee: Dan Smith
>Priority: Major
> Labels: CI
>
> Test failed in CI run
> [308|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/308]
> {noformat}
> org.apache.geode.cache.query.cq.dunit.CqResultSetUsingPoolOptimizedExecuteDUnitTest
> > testCqResultsCachingForMultipleCQs FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache.query.cq.dunit.CqResultSetUsingPoolDUnitTest$13.run in
> VM 0 running on Host 1d74fe6e98cf with 4 VMs
> Caused by:
> java.lang.AssertionError: The number of keys cached for cq
> testCqResultsP_1 is wrong. expected:<500> but was:<499>
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9911) Allow ExecutorServiceRule to name threads
[
https://issues.apache.org/jira/browse/GEODE-9911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-9911:
--
Labels: pull-request-available (was: )
> Allow ExecutorServiceRule to name threads
> -
>
> Key: GEODE-9911
> URL: https://issues.apache.org/jira/browse/GEODE-9911
> Project: Geode
> Issue Type: Test
> Components: tests
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
> Labels: pull-request-available
>
> In some situations it may be useful to name the threads created by the
> {{{}ExecutorServiceRule{}}}. These would appear in log files and be helpful
> in debugging.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9859) Mass-Test-Run: WanCopyRegionCommandDUnitTest.testRegionDestroyedDuringExecution(false, false) [0] FAILED
[
https://issues.apache.org/jira/browse/GEODE-9859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468193#comment-17468193
]
Geode Integration commented on GEODE-9859:
--
Seen in [distributed-test-openjdk8
#545|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/545]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0753/test-results/distributedTest/1641058918/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0753/test-artifacts/1641058918/distributedtestfiles-openjdk8-1.15.0-build.0753.tgz].
> Mass-Test-Run:
> WanCopyRegionCommandDUnitTest.testRegionDestroyedDuringExecution(false,
> false) [0] FAILED
>
>
> Key: GEODE-9859
> URL: https://issues.apache.org/jira/browse/GEODE-9859
> Project: Geode
> Issue Type: Bug
> Components: wan
>Affects Versions: 1.15.0
>Reporter: Mark Hanson
>Assignee: Alberto Gomez
>Priority: Major
> Labels: pull-request-available
>
> Looks like this might be failing from the original PR. I have linked to
> GEODE-9369 as the most likely origination.
>
> {noformat}
> WanCopyRegionCommandDUnitTest > testRegionDestroyedDuringExecution(false,
> false) [0] FAILED
> java.lang.AssertionError:
> Expecting elements:
> ["Execution failed. Error:
> org.apache.geode.cache.EntryDestroyedException: 937"]
> to have exactly 1 times execution error
> at
> org.apache.geode.cache.wan.internal.cli.commands.WanCopyRegionCommandDUnitTest.testRegionDestroyedDuringExecution(WanCopyRegionCommandDUnitTest.java:450)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9885) StringsDUnitTest.givenBucketsMoveDuringAppend_thenDataIsNotLost fails with duplicated append
[
https://issues.apache.org/jira/browse/GEODE-9885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468173#comment-17468173
]
Geode Integration commented on GEODE-9885:
--
Seen in [distributed-test-openjdk8
#501|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/501]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0753/test-results/distributedTest/1641027654/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0753/test-artifacts/1641027654/distributedtestfiles-openjdk8-1.15.0-build.0753.tgz].
> StringsDUnitTest.givenBucketsMoveDuringAppend_thenDataIsNotLost fails with
> duplicated append
>
>
> Key: GEODE-9885
> URL: https://issues.apache.org/jira/browse/GEODE-9885
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Ray Ingles
>Priority: Major
> Labels: needsTriage
>
> The test appends a lot of strings to a key. It wound up adding (at least one)
> extra string to the stored string:
>
> {{java.util.concurrent.ExecutionException: java.lang.AssertionError:
> unexpected -\{append0}-key-3-27680- at index 27681 iterationCount=61995 in
> string}}
>
> The string "\{append0}-key-3-27680-" appeared twice in sequence.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-8644) SerialGatewaySenderQueueDUnitTest.unprocessedTokensMapShouldDrainCompletely() intermittently fails when queues drain too slowly
[ https://issues.apache.org/jira/browse/GEODE-8644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468172#comment-17468172 ] Geode Integration commented on GEODE-8644: -- Seen in [distributed-test-openjdk8 #587|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/587] ... see [test results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0753/test-results/distributedTest/1641091232/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0753/test-artifacts/1641091232/distributedtestfiles-openjdk8-1.15.0-build.0753.tgz]. > SerialGatewaySenderQueueDUnitTest.unprocessedTokensMapShouldDrainCompletely() > intermittently fails when queues drain too slowly > --- > > Key: GEODE-8644 > URL: https://issues.apache.org/jira/browse/GEODE-8644 > Project: Geode > Issue Type: Bug >Affects Versions: 1.15.0 >Reporter: Benjamin P Ross >Assignee: Xiaojian Zhou >Priority: Major > Labels: GeodeOperationAPI, needsTriage, pull-request-available > > Currently the test > SerialGatewaySenderQueueDUnitTest.unprocessedTokensMapShouldDrainCompletely() > relies on a 2 second delay to allow for queues to finish draining after > finishing the put operation. If queues take longer than 2 seconds to drain > the test will fail. We should change the test to wait for the queues to be > empty with a long timeout in case the queues never fully drain. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-8644) SerialGatewaySenderQueueDUnitTest.unprocessedTokensMapShouldDrainCompletely() intermittently fails when queues drain too slowly
[ https://issues.apache.org/jira/browse/GEODE-8644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468171#comment-17468171 ] Geode Integration commented on GEODE-8644: -- Seen in [distributed-test-openjdk8 #588|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/588] ... see [test results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0753/test-results/distributedTest/1641091689/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0753/test-artifacts/1641091689/distributedtestfiles-openjdk8-1.15.0-build.0753.tgz]. > SerialGatewaySenderQueueDUnitTest.unprocessedTokensMapShouldDrainCompletely() > intermittently fails when queues drain too slowly > --- > > Key: GEODE-8644 > URL: https://issues.apache.org/jira/browse/GEODE-8644 > Project: Geode > Issue Type: Bug >Affects Versions: 1.15.0 >Reporter: Benjamin P Ross >Assignee: Xiaojian Zhou >Priority: Major > Labels: GeodeOperationAPI, needsTriage, pull-request-available > > Currently the test > SerialGatewaySenderQueueDUnitTest.unprocessedTokensMapShouldDrainCompletely() > relies on a 2 second delay to allow for queues to finish draining after > finishing the put operation. If queues take longer than 2 seconds to drain > the test will fail. We should change the test to wait for the queues to be > empty with a long timeout in case the queues never fully drain. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9885) StringsDUnitTest.givenBucketsMoveDuringAppend_thenDataIsNotLost fails with duplicated append
[
https://issues.apache.org/jira/browse/GEODE-9885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468165#comment-17468165
]
Geode Integration commented on GEODE-9885:
--
Seen in [distributed-test-openjdk8
#543|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/543]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0753/test-results/distributedTest/1641058847/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0753/test-artifacts/1641058847/distributedtestfiles-openjdk8-1.15.0-build.0753.tgz].
> StringsDUnitTest.givenBucketsMoveDuringAppend_thenDataIsNotLost fails with
> duplicated append
>
>
> Key: GEODE-9885
> URL: https://issues.apache.org/jira/browse/GEODE-9885
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Ray Ingles
>Priority: Major
> Labels: needsTriage
>
> The test appends a lot of strings to a key. It wound up adding (at least one)
> extra string to the stored string:
>
> {{java.util.concurrent.ExecutionException: java.lang.AssertionError:
> unexpected -\{append0}-key-3-27680- at index 27681 iterationCount=61995 in
> string}}
>
> The string "\{append0}-key-3-27680-" appeared twice in sequence.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (GEODE-9911) Allow ExecutorServiceRule to name threads
[
https://issues.apache.org/jira/browse/GEODE-9911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jens Deppe reassigned GEODE-9911:
-
Assignee: Jens Deppe
> Allow ExecutorServiceRule to name threads
> -
>
> Key: GEODE-9911
> URL: https://issues.apache.org/jira/browse/GEODE-9911
> Project: Geode
> Issue Type: Test
> Components: tests
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
>
> In some situations it may be useful to name the threads created by the
> {{{}ExecutorServiceRule{}}}. These would appear in log files and be helpful
> in debugging.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (GEODE-9911) Allow ExecutorServiceRule to name threads
Jens Deppe created GEODE-9911:
-
Summary: Allow ExecutorServiceRule to name threads
Key: GEODE-9911
URL: https://issues.apache.org/jira/browse/GEODE-9911
Project: Geode
Issue Type: Test
Components: tests
Reporter: Jens Deppe
In some situations it may be useful to name the threads created by the
{{{}ExecutorServiceRule{}}}. These would appear in log files and be helpful in
debugging.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9908) Marker message is delivered to the durable client after all the puts messages
[ https://issues.apache.org/jira/browse/GEODE-9908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-9908: -- Labels: pull-request-available (was: ) > Marker message is delivered to the durable client after all the puts messages > - > > Key: GEODE-9908 > URL: https://issues.apache.org/jira/browse/GEODE-9908 > Project: Geode > Issue Type: Bug > Components: client queues >Reporter: Jinmei Liao >Priority: Major > Labels: pull-request-available > > When a durable client with registered interests, connects to the server: > 1. it sends a readyForEvent message to the queue, the sever enqueues a marker > message. > 2. then the server enqueues all the puts messages to the queue. > 3. the client disconnects (either by connection failure or by re-auth failure) > 4. the client reconnects back to another server, the other server makes its > queue primary, and enqueues another marker message. > 5. if the first marker message hasn't been delivered to the client yet, the > queue manager will delete the first marker message since marker messages > should be conflated. Then all puts messages will be delivered before the > marker message, thus the client won't put the values in its client cache. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9060) checkMyStateOnMemebers is better not to change the replicates
[ https://issues.apache.org/jira/browse/GEODE-9060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468143#comment-17468143 ] ASF subversion and git services commented on GEODE-9060: Commit faf056d657463cdfee50e402a3861ed86e232f09 in geode's branch refs/heads/feature/GEODE-9060 from Xiaojian Zhou [ https://gitbox.apache.org/repos/asf?p=geode.git;h=faf056d ] GEODE-9060: Remove the member from a copy of replicates as GII candid… (#6246) * GEODE-9060: Remove the member from a copy of replicates as GII candidate if it's not part of the same distributed system, but leave original replicates unchanged. (cherry picked from commit 76a5afddc9eaecea9f0b4528a910eb6761e1a3a1) > checkMyStateOnMemebers is better not to change the replicates > - > > Key: GEODE-9060 > URL: https://issues.apache.org/jira/browse/GEODE-9060 > Project: Geode > Issue Type: Bug >Reporter: Xiaojian Zhou >Assignee: Xiaojian Zhou >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > Fix For: 1.15.0 > > > This is an enhancement to previous GEODE-9003. > The previous fix will remove the members in replicates if it cannot recognize > current member, thus these removed members will not acting as GII provider > candidates. The fix is correct. > However, Dan suggested to keep the replicates as is to be more conservative. > These members will still act as GII provider candidates even they cannot > recognize current member due to the split-brain. Conceptually these members > should be the same as other online members. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9908) Marker message is delivered to the durable client after all the puts messages
[ https://issues.apache.org/jira/browse/GEODE-9908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468128#comment-17468128 ] Jinmei Liao commented on GEODE-9908: https://github.com/apache/geode/pull/7213 > Marker message is delivered to the durable client after all the puts messages > - > > Key: GEODE-9908 > URL: https://issues.apache.org/jira/browse/GEODE-9908 > Project: Geode > Issue Type: Bug > Components: client queues >Reporter: Jinmei Liao >Priority: Major > > When a durable client with registered interests, connects to the server: > 1. it sends a readyForEvent message to the queue, the sever enqueues a marker > message. > 2. then the server enqueues all the puts messages to the queue. > 3. the client disconnects (either by connection failure or by re-auth failure) > 4. the client reconnects back to another server, the other server makes its > queue primary, and enqueues another marker message. > 5. if the first marker message hasn't been delivered to the client yet, the > queue manager will delete the first marker message since marker messages > should be conflated. Then all puts messages will be delivered before the > marker message, thus the client won't put the values in its client cache. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9901) Failing upgrade-test after Log4j 2.15 bump to 2.16
[ https://issues.apache.org/jira/browse/GEODE-9901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468115#comment-17468115 ] Geode Integration commented on GEODE-9901: -- Seen on support/1.13 in [upgrade-test-openjdk8 #15|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-main/jobs/upgrade-test-openjdk8/builds/15] ... see [test results|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.7-build.0633/test-results/upgradeTest/1641035799/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.7-build.0633/test-artifacts/1641035799/upgradetestfiles-openjdk8-1.13.7-build.0633.tgz]. > Failing upgrade-test after Log4j 2.15 bump to 2.16 > -- > > Key: GEODE-9901 > URL: https://issues.apache.org/jira/browse/GEODE-9901 > Project: Geode > Issue Type: Bug >Affects Versions: 1.13.6 >Reporter: Steve Sienkowski >Priority: Major > > A number of tests are failing in the `upgrade-test-openjdk11` job of the 1.13 > pipeline. > These issues are characterized by an error message of > `java.rmi.ConnectException: Connection refused to host:` > First failure here: > [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-main/jobs/upgrade-test-openjdk11/builds/14] > Git commit introducing upgrade of log4j 2.15 to 2.16: > [https://github.com/apache/geode/commit/224c996daa8bdd5243399e7d929120ad99c39fe3] > Relevant JIRA: https://issues.apache.org/jira/browse/GEODE-9898 > > > > Example error message: > > Task :geode-gfsh:upgradeTest > org.apache.geode.management.GfshRebalanceCommandCompatibilityTest > > whenCurrentVersionLocatorsExecuteRebalanceOnOldServersThenItMustSucceed[1.12.0] > FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.test.dunit.IgnoredException$1.run in VM 0 running on Host > c9ef3b85f95a with 4 VMs with version 1.12.0 > Caused by: > java.rmi.ConnectException: Connection refused to host: 172.17.0.37; > nested exception is: > java.net.ConnectException: Connection refused (Connection refused) > Caused by: > java.net.ConnectException: Connection refused (Connection refused) -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9901) Failing upgrade-test after Log4j 2.15 bump to 2.16
[ https://issues.apache.org/jira/browse/GEODE-9901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468114#comment-17468114 ] Geode Integration commented on GEODE-9901: -- Seen on support/1.13 in [upgrade-test-openjdk11 #38|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-main/jobs/upgrade-test-openjdk11/builds/38] ... see [test results|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.7-build.0632/test-results/upgradeTest/1640848564/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.7-build.0632/test-artifacts/1640848564/upgradetestfiles-openjdk11-1.13.7-build.0632.tgz]. > Failing upgrade-test after Log4j 2.15 bump to 2.16 > -- > > Key: GEODE-9901 > URL: https://issues.apache.org/jira/browse/GEODE-9901 > Project: Geode > Issue Type: Bug >Affects Versions: 1.13.6 >Reporter: Steve Sienkowski >Priority: Major > > A number of tests are failing in the `upgrade-test-openjdk11` job of the 1.13 > pipeline. > These issues are characterized by an error message of > `java.rmi.ConnectException: Connection refused to host:` > First failure here: > [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-main/jobs/upgrade-test-openjdk11/builds/14] > Git commit introducing upgrade of log4j 2.15 to 2.16: > [https://github.com/apache/geode/commit/224c996daa8bdd5243399e7d929120ad99c39fe3] > Relevant JIRA: https://issues.apache.org/jira/browse/GEODE-9898 > > > > Example error message: > > Task :geode-gfsh:upgradeTest > org.apache.geode.management.GfshRebalanceCommandCompatibilityTest > > whenCurrentVersionLocatorsExecuteRebalanceOnOldServersThenItMustSucceed[1.12.0] > FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.test.dunit.IgnoredException$1.run in VM 0 running on Host > c9ef3b85f95a with 4 VMs with version 1.12.0 > Caused by: > java.rmi.ConnectException: Connection refused to host: 172.17.0.37; > nested exception is: > java.net.ConnectException: Connection refused (Connection refused) > Caused by: > java.net.ConnectException: Connection refused (Connection refused) -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9901) Failing upgrade-test after Log4j 2.15 bump to 2.16
[ https://issues.apache.org/jira/browse/GEODE-9901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468116#comment-17468116 ] Geode Integration commented on GEODE-9901: -- Seen on support/1.13 in [upgrade-test-openjdk11 #40|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-main/jobs/upgrade-test-openjdk11/builds/40] ... see [test results|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.7-build.0633/test-results/upgradeTest/1641096883/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.7-build.0633/test-artifacts/1641096883/upgradetestfiles-openjdk11-1.13.7-build.0633.tgz]. > Failing upgrade-test after Log4j 2.15 bump to 2.16 > -- > > Key: GEODE-9901 > URL: https://issues.apache.org/jira/browse/GEODE-9901 > Project: Geode > Issue Type: Bug >Affects Versions: 1.13.6 >Reporter: Steve Sienkowski >Priority: Major > > A number of tests are failing in the `upgrade-test-openjdk11` job of the 1.13 > pipeline. > These issues are characterized by an error message of > `java.rmi.ConnectException: Connection refused to host:` > First failure here: > [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-main/jobs/upgrade-test-openjdk11/builds/14] > Git commit introducing upgrade of log4j 2.15 to 2.16: > [https://github.com/apache/geode/commit/224c996daa8bdd5243399e7d929120ad99c39fe3] > Relevant JIRA: https://issues.apache.org/jira/browse/GEODE-9898 > > > > Example error message: > > Task :geode-gfsh:upgradeTest > org.apache.geode.management.GfshRebalanceCommandCompatibilityTest > > whenCurrentVersionLocatorsExecuteRebalanceOnOldServersThenItMustSucceed[1.12.0] > FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.test.dunit.IgnoredException$1.run in VM 0 running on Host > c9ef3b85f95a with 4 VMs with version 1.12.0 > Caused by: > java.rmi.ConnectException: Connection refused to host: 172.17.0.37; > nested exception is: > java.net.ConnectException: Connection refused (Connection refused) > Caused by: > java.net.ConnectException: Connection refused (Connection refused) -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9901) Failing upgrade-test after Log4j 2.15 bump to 2.16
[ https://issues.apache.org/jira/browse/GEODE-9901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468113#comment-17468113 ] Geode Integration commented on GEODE-9901: -- Seen on support/1.13 in [upgrade-test-openjdk11 #37|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-main/jobs/upgrade-test-openjdk11/builds/37] ... see [test results|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.7-build.0632/test-results/upgradeTest/1640821075/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.7-build.0632/test-artifacts/1640821075/upgradetestfiles-openjdk11-1.13.7-build.0632.tgz]. > Failing upgrade-test after Log4j 2.15 bump to 2.16 > -- > > Key: GEODE-9901 > URL: https://issues.apache.org/jira/browse/GEODE-9901 > Project: Geode > Issue Type: Bug >Affects Versions: 1.13.6 >Reporter: Steve Sienkowski >Priority: Major > > A number of tests are failing in the `upgrade-test-openjdk11` job of the 1.13 > pipeline. > These issues are characterized by an error message of > `java.rmi.ConnectException: Connection refused to host:` > First failure here: > [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-main/jobs/upgrade-test-openjdk11/builds/14] > Git commit introducing upgrade of log4j 2.15 to 2.16: > [https://github.com/apache/geode/commit/224c996daa8bdd5243399e7d929120ad99c39fe3] > Relevant JIRA: https://issues.apache.org/jira/browse/GEODE-9898 > > > > Example error message: > > Task :geode-gfsh:upgradeTest > org.apache.geode.management.GfshRebalanceCommandCompatibilityTest > > whenCurrentVersionLocatorsExecuteRebalanceOnOldServersThenItMustSucceed[1.12.0] > FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.test.dunit.IgnoredException$1.run in VM 0 running on Host > c9ef3b85f95a with 4 VMs with version 1.12.0 > Caused by: > java.rmi.ConnectException: Connection refused to host: 172.17.0.37; > nested exception is: > java.net.ConnectException: Connection refused (Connection refused) > Caused by: > java.net.ConnectException: Connection refused (Connection refused) -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9901) Failing upgrade-test after Log4j 2.15 bump to 2.16
[ https://issues.apache.org/jira/browse/GEODE-9901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468110#comment-17468110 ] Geode Integration commented on GEODE-9901: -- Seen on support/1.13 in [upgrade-test-openjdk11 #35|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-main/jobs/upgrade-test-openjdk11/builds/35] ... see [test results|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.7-build.0631/test-results/upgradeTest/1640228313/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.7-build.0631/test-artifacts/1640228313/upgradetestfiles-openjdk11-1.13.7-build.0631.tgz]. > Failing upgrade-test after Log4j 2.15 bump to 2.16 > -- > > Key: GEODE-9901 > URL: https://issues.apache.org/jira/browse/GEODE-9901 > Project: Geode > Issue Type: Bug >Affects Versions: 1.13.6 >Reporter: Steve Sienkowski >Priority: Major > > A number of tests are failing in the `upgrade-test-openjdk11` job of the 1.13 > pipeline. > These issues are characterized by an error message of > `java.rmi.ConnectException: Connection refused to host:` > First failure here: > [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-main/jobs/upgrade-test-openjdk11/builds/14] > Git commit introducing upgrade of log4j 2.15 to 2.16: > [https://github.com/apache/geode/commit/224c996daa8bdd5243399e7d929120ad99c39fe3] > Relevant JIRA: https://issues.apache.org/jira/browse/GEODE-9898 > > > > Example error message: > > Task :geode-gfsh:upgradeTest > org.apache.geode.management.GfshRebalanceCommandCompatibilityTest > > whenCurrentVersionLocatorsExecuteRebalanceOnOldServersThenItMustSucceed[1.12.0] > FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.test.dunit.IgnoredException$1.run in VM 0 running on Host > c9ef3b85f95a with 4 VMs with version 1.12.0 > Caused by: > java.rmi.ConnectException: Connection refused to host: 172.17.0.37; > nested exception is: > java.net.ConnectException: Connection refused (Connection refused) > Caused by: > java.net.ConnectException: Connection refused (Connection refused) -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9901) Failing upgrade-test after Log4j 2.15 bump to 2.16
[ https://issues.apache.org/jira/browse/GEODE-9901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468109#comment-17468109 ] Geode Integration commented on GEODE-9901: -- Seen on support/1.13 in [upgrade-test-openjdk11 #34|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-main/jobs/upgrade-test-openjdk11/builds/34] ... see [test results|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.7-build.0631/test-results/upgradeTest/1640221456/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.7-build.0631/test-artifacts/1640221456/upgradetestfiles-openjdk11-1.13.7-build.0631.tgz]. > Failing upgrade-test after Log4j 2.15 bump to 2.16 > -- > > Key: GEODE-9901 > URL: https://issues.apache.org/jira/browse/GEODE-9901 > Project: Geode > Issue Type: Bug >Affects Versions: 1.13.6 >Reporter: Steve Sienkowski >Priority: Major > > A number of tests are failing in the `upgrade-test-openjdk11` job of the 1.13 > pipeline. > These issues are characterized by an error message of > `java.rmi.ConnectException: Connection refused to host:` > First failure here: > [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-main/jobs/upgrade-test-openjdk11/builds/14] > Git commit introducing upgrade of log4j 2.15 to 2.16: > [https://github.com/apache/geode/commit/224c996daa8bdd5243399e7d929120ad99c39fe3] > Relevant JIRA: https://issues.apache.org/jira/browse/GEODE-9898 > > > > Example error message: > > Task :geode-gfsh:upgradeTest > org.apache.geode.management.GfshRebalanceCommandCompatibilityTest > > whenCurrentVersionLocatorsExecuteRebalanceOnOldServersThenItMustSucceed[1.12.0] > FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.test.dunit.IgnoredException$1.run in VM 0 running on Host > c9ef3b85f95a with 4 VMs with version 1.12.0 > Caused by: > java.rmi.ConnectException: Connection refused to host: 172.17.0.37; > nested exception is: > java.net.ConnectException: Connection refused (Connection refused) > Caused by: > java.net.ConnectException: Connection refused (Connection refused) -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9901) Failing upgrade-test after Log4j 2.15 bump to 2.16
[ https://issues.apache.org/jira/browse/GEODE-9901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468112#comment-17468112 ] Geode Integration commented on GEODE-9901: -- Seen on support/1.13 in [upgrade-test-openjdk11 #36|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-main/jobs/upgrade-test-openjdk11/builds/36] ... see [test results|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.7-build.0631/test-results/upgradeTest/1640817575/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.7-build.0631/test-artifacts/1640817575/upgradetestfiles-openjdk11-1.13.7-build.0631.tgz]. > Failing upgrade-test after Log4j 2.15 bump to 2.16 > -- > > Key: GEODE-9901 > URL: https://issues.apache.org/jira/browse/GEODE-9901 > Project: Geode > Issue Type: Bug >Affects Versions: 1.13.6 >Reporter: Steve Sienkowski >Priority: Major > > A number of tests are failing in the `upgrade-test-openjdk11` job of the 1.13 > pipeline. > These issues are characterized by an error message of > `java.rmi.ConnectException: Connection refused to host:` > First failure here: > [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-main/jobs/upgrade-test-openjdk11/builds/14] > Git commit introducing upgrade of log4j 2.15 to 2.16: > [https://github.com/apache/geode/commit/224c996daa8bdd5243399e7d929120ad99c39fe3] > Relevant JIRA: https://issues.apache.org/jira/browse/GEODE-9898 > > > > Example error message: > > Task :geode-gfsh:upgradeTest > org.apache.geode.management.GfshRebalanceCommandCompatibilityTest > > whenCurrentVersionLocatorsExecuteRebalanceOnOldServersThenItMustSucceed[1.12.0] > FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.test.dunit.IgnoredException$1.run in VM 0 running on Host > c9ef3b85f95a with 4 VMs with version 1.12.0 > Caused by: > java.rmi.ConnectException: Connection refused to host: 172.17.0.37; > nested exception is: > java.net.ConnectException: Connection refused (Connection refused) > Caused by: > java.net.ConnectException: Connection refused (Connection refused) -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (GEODE-9907) Geode-for-redis example failed with JedisNoReachableClusterNodeException: No reachable node in cluster
[
https://issues.apache.org/jira/browse/GEODE-9907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donal Evans updated GEODE-9907:
---
Labels: needsTriage (was: triage)
> Geode-for-redis example failed with JedisNoReachableClusterNodeException: No
> reachable node in cluster
> --
>
> Key: GEODE-9907
> URL: https://issues.apache.org/jira/browse/GEODE-9907
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Kristen
>Assignee: Donal Evans
>Priority: Major
> Labels: needsTriage
>
>
> {code:java}
> > Task :geodeForRedis:run FAILED
> Exception in thread "main"
> redis.clients.jedis.exceptions.JedisNoReachableClusterNodeException: No
> reachable node in cluster
> at
> redis.clients.jedis.JedisSlotBasedConnectionHandler.getConnection(JedisSlotBasedConnectionHandler.java:117)
> at
> redis.clients.jedis.JedisSlotBasedConnectionHandler.getConnectionFromSlot(JedisSlotBasedConnectionHandler.java:139)
> at
> redis.clients.jedis.JedisClusterCommand.runWithRetries(JedisClusterCommand.java:118)
> at redis.clients.jedis.JedisClusterCommand.run(JedisClusterCommand.java:45)
> at redis.clients.jedis.JedisCluster.zadd(JedisCluster.java:1106)
> at
> org.apache.geode_examples.geodeForRedis.Example.populateSortedSet(Example.java:53)
> at org.apache.geode_examples.geodeForRedis.Example.main(Example.java:30)
> FAILURE: Build failed with an exception.
> * What went wrong:
> Execution failed for task ':geodeForRedis:run'.
> > Process 'command '/usr/lib/jvm/bellsoft-java8-amd64/bin/java'' finished
> >with non-zero exit value 1
> {code}
>
> This might be related to [https://github.com/apache/geode-examples/pull/110]
> due to the location of the failure of the test
> org.apache.geode_examples.geodeForRedis.Example.main.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9901) Failing upgrade-test after Log4j 2.15 bump to 2.16
[ https://issues.apache.org/jira/browse/GEODE-9901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468107#comment-17468107 ] Owen Nichols commented on GEODE-9901: - suspecting this may be related to "too many old versions"...let's see if this calms down after the old-versions list is pared down on Jan 5 (see dev list discussion) > Failing upgrade-test after Log4j 2.15 bump to 2.16 > -- > > Key: GEODE-9901 > URL: https://issues.apache.org/jira/browse/GEODE-9901 > Project: Geode > Issue Type: Bug >Affects Versions: 1.13.6 >Reporter: Steve Sienkowski >Priority: Major > > A number of tests are failing in the `upgrade-test-openjdk11` job of the 1.13 > pipeline. > These issues are characterized by an error message of > `java.rmi.ConnectException: Connection refused to host:` > First failure here: > [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-main/jobs/upgrade-test-openjdk11/builds/14] > Git commit introducing upgrade of log4j 2.15 to 2.16: > [https://github.com/apache/geode/commit/224c996daa8bdd5243399e7d929120ad99c39fe3] > Relevant JIRA: https://issues.apache.org/jira/browse/GEODE-9898 > > > > Example error message: > > Task :geode-gfsh:upgradeTest > org.apache.geode.management.GfshRebalanceCommandCompatibilityTest > > whenCurrentVersionLocatorsExecuteRebalanceOnOldServersThenItMustSucceed[1.12.0] > FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.test.dunit.IgnoredException$1.run in VM 0 running on Host > c9ef3b85f95a with 4 VMs with version 1.12.0 > Caused by: > java.rmi.ConnectException: Connection refused to host: 172.17.0.37; > nested exception is: > java.net.ConnectException: Connection refused (Connection refused) > Caused by: > java.net.ConnectException: Connection refused (Connection refused) -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Reopened] (GEODE-9060) checkMyStateOnMemebers is better not to change the replicates
[ https://issues.apache.org/jira/browse/GEODE-9060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiaojian Zhou reopened GEODE-9060: -- Need to backport it to 1.12, 1.13, 1.14 according to the requirements. > checkMyStateOnMemebers is better not to change the replicates > - > > Key: GEODE-9060 > URL: https://issues.apache.org/jira/browse/GEODE-9060 > Project: Geode > Issue Type: Bug >Reporter: Xiaojian Zhou >Assignee: Xiaojian Zhou >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > Fix For: 1.15.0 > > > This is an enhancement to previous GEODE-9003. > The previous fix will remove the members in replicates if it cannot recognize > current member, thus these removed members will not acting as GII provider > candidates. The fix is correct. > However, Dan suggested to keep the replicates as is to be more conservative. > These members will still act as GII provider candidates even they cannot > recognize current member due to the split-brain. Conceptually these members > should be the same as other online members. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (GEODE-9907) Geode-for-redis example failed with JedisNoReachableClusterNodeException: No reachable node in cluster
[
https://issues.apache.org/jira/browse/GEODE-9907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donal Evans reassigned GEODE-9907:
--
Assignee: Donal Evans
> Geode-for-redis example failed with JedisNoReachableClusterNodeException: No
> reachable node in cluster
> --
>
> Key: GEODE-9907
> URL: https://issues.apache.org/jira/browse/GEODE-9907
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Kristen
>Assignee: Donal Evans
>Priority: Major
> Labels: triage
>
>
> {code:java}
> > Task :geodeForRedis:run FAILED
> Exception in thread "main"
> redis.clients.jedis.exceptions.JedisNoReachableClusterNodeException: No
> reachable node in cluster
> at
> redis.clients.jedis.JedisSlotBasedConnectionHandler.getConnection(JedisSlotBasedConnectionHandler.java:117)
> at
> redis.clients.jedis.JedisSlotBasedConnectionHandler.getConnectionFromSlot(JedisSlotBasedConnectionHandler.java:139)
> at
> redis.clients.jedis.JedisClusterCommand.runWithRetries(JedisClusterCommand.java:118)
> at redis.clients.jedis.JedisClusterCommand.run(JedisClusterCommand.java:45)
> at redis.clients.jedis.JedisCluster.zadd(JedisCluster.java:1106)
> at
> org.apache.geode_examples.geodeForRedis.Example.populateSortedSet(Example.java:53)
> at org.apache.geode_examples.geodeForRedis.Example.main(Example.java:30)
> FAILURE: Build failed with an exception.
> * What went wrong:
> Execution failed for task ':geodeForRedis:run'.
> > Process 'command '/usr/lib/jvm/bellsoft-java8-amd64/bin/java'' finished
> >with non-zero exit value 1
> {code}
>
> This might be related to [https://github.com/apache/geode-examples/pull/110]
> due to the location of the failure of the test
> org.apache.geode_examples.geodeForRedis.Example.main.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (GEODE-9907) Geode-for-redis example failed with JedisNoReachableClusterNodeException: No reachable node in cluster
[
https://issues.apache.org/jira/browse/GEODE-9907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donal Evans updated GEODE-9907:
---
Summary: Geode-for-redis example failed with
JedisNoReachableClusterNodeException: No reachable node in cluster (was:
'command '/usr/lib/jvm/bellsoft-java8-amd64/bin/java'' finished with non-zero
exit value 1)
> Geode-for-redis example failed with JedisNoReachableClusterNodeException: No
> reachable node in cluster
> --
>
> Key: GEODE-9907
> URL: https://issues.apache.org/jira/browse/GEODE-9907
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Kristen
>Priority: Major
> Labels: triage
>
>
> {code:java}
> > Task :geodeForRedis:run FAILED
> Exception in thread "main"
> redis.clients.jedis.exceptions.JedisNoReachableClusterNodeException: No
> reachable node in cluster
> at
> redis.clients.jedis.JedisSlotBasedConnectionHandler.getConnection(JedisSlotBasedConnectionHandler.java:117)
> at
> redis.clients.jedis.JedisSlotBasedConnectionHandler.getConnectionFromSlot(JedisSlotBasedConnectionHandler.java:139)
> at
> redis.clients.jedis.JedisClusterCommand.runWithRetries(JedisClusterCommand.java:118)
> at redis.clients.jedis.JedisClusterCommand.run(JedisClusterCommand.java:45)
> at redis.clients.jedis.JedisCluster.zadd(JedisCluster.java:1106)
> at
> org.apache.geode_examples.geodeForRedis.Example.populateSortedSet(Example.java:53)
> at org.apache.geode_examples.geodeForRedis.Example.main(Example.java:30)
> FAILURE: Build failed with an exception.
> * What went wrong:
> Execution failed for task ':geodeForRedis:run'.
> > Process 'command '/usr/lib/jvm/bellsoft-java8-amd64/bin/java'' finished
> >with non-zero exit value 1
> {code}
>
> This might be related to [https://github.com/apache/geode-examples/pull/110]
> due to the location of the failure of the test
> org.apache.geode_examples.geodeForRedis.Example.main.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (GEODE-9910) Failure to auto-reconnect upon network partition
[ https://issues.apache.org/jira/browse/GEODE-9910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468093#comment-17468093 ] Anthony Baker commented on GEODE-9910: -- This seems like a potential race condition during auto-reconnect after a network partition with embedded locators. > Failure to auto-reconnect upon network partition > > > Key: GEODE-9910 > URL: https://issues.apache.org/jira/browse/GEODE-9910 > Project: Geode > Issue Type: Bug >Affects Versions: 1.14.0 >Reporter: Surya Mudundi >Priority: Major > > Two node cluster with embedded locators failed to auto-reconnect when node-1 > experienced network outage for couple of minutes and when node-1 recovered > from the outage, node-2 failed to auto-reconnect. > node-2 tried to re-connect to node-1 as: > [org.apache.geode.distributed.internal.InternalDistributedSystem]-[ReconnectThread] > [] Attempting to reconnect to the distributed system. This is attempt #1. > [org.apache.geode.distributed.internal.InternalDistributedSystem]-[ReconnectThread] > [] Attempting to reconnect to the distributed system. This is attempt #2. > [org.apache.geode.distributed.internal.InternalDistributedSystem]-[ReconnectThread] > [] Attempting to reconnect to the distributed system. This is attempt #3. > Finally reported below error after 3 attempts as: > INFO > [org.apache.geode.logging.internal.LoggingProviderLoader]-[ReconnectThread] > [] Using org.apache.geode.logging.internal.SimpleLoggingProvider for service > org.apache.geode.logging.internal.spi.LoggingProvider > INFO [org.apache.geode.internal.InternalDataSerializer]-[ReconnectThread] [] > initializing InternalDataSerializer with 0 services > INFO > [org.apache.geode.distributed.internal.InternalDistributedSystem]-[ReconnectThread] > [] performing a quorum check to see if location services can be started early > INFO > [org.apache.geode.distributed.internal.InternalDistributedSystem]-[ReconnectThread] > [] Quorum check passed - allowing location services to start early > WARN > [org.apache.geode.distributed.internal.InternalDistributedSystem]-[ReconnectThread] > [] Exception occurred while trying to connect the system during reconnect > java.lang.IllegalStateException: A locator can not be created because one > already exists in this JVM. > at > org.apache.geode.distributed.internal.InternalLocator.createLocator(InternalLocator.java:298) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalLocator.createLocator(InternalLocator.java:273) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalDistributedSystem.startInitLocator(InternalDistributedSystem.java:916) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:768) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalDistributedSystem.access$200(InternalDistributedSystem.java:135) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalDistributedSystem$Builder.build(InternalDistributedSystem.java:3034) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalDistributedSystem.connectInternal(InternalDistributedSystem.java:290) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalDistributedSystem.reconnect(InternalDistributedSystem.java:2605) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalDistributedSystem.tryReconnect(InternalDistributedSystem.java:2424) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1275) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.ClusterDistributionManager$DMListener.membershipFailure(ClusterDistributionManager.java:2326) > ~[geode-core-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.membership.gms.GMSMembership.uncleanShutdown(GMSMembership.java:1187) > ~[geode-membership-1.14.0.jar:?] > at > org.apache.geode.distributed.internal.membership.gms.GMSMembership$ManagerImpl.lambda$forceDisconnect$0(GMSMembership.java:1811) > ~[geode-membership-1.14.0.jar:?] > at java.lang.Thread.run(Thread.java:829) [?:?] > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (GEODE-9502) Eliminate templates used to work around now-obsolete MSVC compiler warning
[
https://issues.apache.org/jira/browse/GEODE-9502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468081#comment-17468081
]
ASF GitHub Bot commented on GEODE-9502:
---
mreddington commented on a change in pull request #901:
URL: https://github.com/apache/geode-native/pull/901#discussion_r777568726
##
File path: cppcache/integration/framework/Cluster.cpp
##
@@ -146,7 +146,10 @@ void Locator::start() {
}
void Locator::stop() {
- cluster_.getGfsh().stop().locator().withDir(name_).execute();
+ try {
+cluster_.getGfsh().stop().locator().withDir(name_).execute();
+ } catch (...) {
Review comment:
Destructors aren't supposed to throw. We throw an exception when
BOOST_PROCESS tries to execute a command on a locator and the locator is
already down. This has absolutely nothing to do with the test itself or the
native client. We aren't testing the cluster, the testing framework itself, or
the environment.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscr...@geode.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Eliminate templates used to work around now-obsolete MSVC compiler warning
> --
>
> Key: GEODE-9502
> URL: https://issues.apache.org/jira/browse/GEODE-9502
> Project: Geode
> Issue Type: Improvement
> Components: native client
>Reporter: Blake Bender
>Priority: Major
> Labels: pull-request-available
>
> CacheableBuiltins.hpp contains the following comment, followed by a bunch of
> very strange template definitions:
> // The following are defined as classes to avoid the issues with MSVC++
> // warning/erroring on C4503
> According to Microsoft
> (https://docs.microsoft.com/en-us/cpp/error-messages/compiler-warnings/compiler-warning-level-1-c4503?view=msvc-160),
> this warning was obsolete as of VS2017. We no longer support any pre-VS2017
> compilers, so it should be safe to remove all this nonsense and replace it
> with the template(s) originally intended.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (GEODE-9910) Failure to auto-reconnect upon network partition
Surya Mudundi created GEODE-9910: Summary: Failure to auto-reconnect upon network partition Key: GEODE-9910 URL: https://issues.apache.org/jira/browse/GEODE-9910 Project: Geode Issue Type: Bug Affects Versions: 1.14.0 Reporter: Surya Mudundi Two node cluster with embedded locators failed to auto-reconnect when node-1 experienced network outage for couple of minutes and when node-1 recovered from the outage, node-2 failed to auto-reconnect. node-2 tried to re-connect to node-1 as: [org.apache.geode.distributed.internal.InternalDistributedSystem]-[ReconnectThread] [] Attempting to reconnect to the distributed system. This is attempt #1. [org.apache.geode.distributed.internal.InternalDistributedSystem]-[ReconnectThread] [] Attempting to reconnect to the distributed system. This is attempt #2. [org.apache.geode.distributed.internal.InternalDistributedSystem]-[ReconnectThread] [] Attempting to reconnect to the distributed system. This is attempt #3. Finally reported below error after 3 attempts as: INFO [org.apache.geode.logging.internal.LoggingProviderLoader]-[ReconnectThread] [] Using org.apache.geode.logging.internal.SimpleLoggingProvider for service org.apache.geode.logging.internal.spi.LoggingProvider INFO [org.apache.geode.internal.InternalDataSerializer]-[ReconnectThread] [] initializing InternalDataSerializer with 0 services INFO [org.apache.geode.distributed.internal.InternalDistributedSystem]-[ReconnectThread] [] performing a quorum check to see if location services can be started early INFO [org.apache.geode.distributed.internal.InternalDistributedSystem]-[ReconnectThread] [] Quorum check passed - allowing location services to start early WARN [org.apache.geode.distributed.internal.InternalDistributedSystem]-[ReconnectThread] [] Exception occurred while trying to connect the system during reconnect java.lang.IllegalStateException: A locator can not be created because one already exists in this JVM. at org.apache.geode.distributed.internal.InternalLocator.createLocator(InternalLocator.java:298) ~[geode-core-1.14.0.jar:?] at org.apache.geode.distributed.internal.InternalLocator.createLocator(InternalLocator.java:273) ~[geode-core-1.14.0.jar:?] at org.apache.geode.distributed.internal.InternalDistributedSystem.startInitLocator(InternalDistributedSystem.java:916) ~[geode-core-1.14.0.jar:?] at org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:768) ~[geode-core-1.14.0.jar:?] at org.apache.geode.distributed.internal.InternalDistributedSystem.access$200(InternalDistributedSystem.java:135) ~[geode-core-1.14.0.jar:?] at org.apache.geode.distributed.internal.InternalDistributedSystem$Builder.build(InternalDistributedSystem.java:3034) ~[geode-core-1.14.0.jar:?] at org.apache.geode.distributed.internal.InternalDistributedSystem.connectInternal(InternalDistributedSystem.java:290) ~[geode-core-1.14.0.jar:?] at org.apache.geode.distributed.internal.InternalDistributedSystem.reconnect(InternalDistributedSystem.java:2605) ~[geode-core-1.14.0.jar:?] at org.apache.geode.distributed.internal.InternalDistributedSystem.tryReconnect(InternalDistributedSystem.java:2424) ~[geode-core-1.14.0.jar:?] at org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1275) ~[geode-core-1.14.0.jar:?] at org.apache.geode.distributed.internal.ClusterDistributionManager$DMListener.membershipFailure(ClusterDistributionManager.java:2326) ~[geode-core-1.14.0.jar:?] at org.apache.geode.distributed.internal.membership.gms.GMSMembership.uncleanShutdown(GMSMembership.java:1187) ~[geode-membership-1.14.0.jar:?] at org.apache.geode.distributed.internal.membership.gms.GMSMembership$ManagerImpl.lambda$forceDisconnect$0(GMSMembership.java:1811) ~[geode-membership-1.14.0.jar:?] at java.lang.Thread.run(Thread.java:829) [?:?] -- This message was sent by Atlassian Jira (v8.20.1#820001)
