[jira] [Commented] (GEODE-7414) SSL ClientHello server_name extension
[
https://issues.apache.org/jira/browse/GEODE-7414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17015157#comment-17015157
]
ASF subversion and git services commented on GEODE-7414:
Commit dddfce0a273a542744b6baab1d3ea535d11894c7 in geode's branch
refs/heads/develop from Mario Ivanac
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=dddfce0 ]
GEODE-7414_1: Define interface (#4505)
* GEODE-7414_1: Introduction of SSL Parameter Extension
- Define interface
- added config parameter
- added SSLParameterExtension implementation
> SSL ClientHello server_name extension
> -
>
> Key: GEODE-7414
> URL: https://issues.apache.org/jira/browse/GEODE-7414
> Project: Geode
> Issue Type: Improvement
> Components: security
>Reporter: Mario Ivanac
>Assignee: Mario Ivanac
>Priority: Major
> Labels: needs-review, pull-request-available
> Time Spent: 1h
> Remaining Estimate: 0h
>
> {color:#172b4d}We propose to add the {color}*server_name extension to the
> ClientHello message*{color:#172b4d}. The extension would hold the distributed
> system ID of the site where the connection originated from.{color}
> {color:#172b4d}This will be used to determine internal geode communication,
> and communication between geode sites.{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7414) SSL ClientHello server_name extension
[
https://issues.apache.org/jira/browse/GEODE-7414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17015156#comment-17015156
]
ASF subversion and git services commented on GEODE-7414:
Commit dddfce0a273a542744b6baab1d3ea535d11894c7 in geode's branch
refs/heads/develop from Mario Ivanac
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=dddfce0 ]
GEODE-7414_1: Define interface (#4505)
* GEODE-7414_1: Introduction of SSL Parameter Extension
- Define interface
- added config parameter
- added SSLParameterExtension implementation
> SSL ClientHello server_name extension
> -
>
> Key: GEODE-7414
> URL: https://issues.apache.org/jira/browse/GEODE-7414
> Project: Geode
> Issue Type: Improvement
> Components: security
>Reporter: Mario Ivanac
>Assignee: Mario Ivanac
>Priority: Major
> Labels: needs-review, pull-request-available
> Time Spent: 1h
> Remaining Estimate: 0h
>
> {color:#172b4d}We propose to add the {color}*server_name extension to the
> ClientHello message*{color:#172b4d}. The extension would hold the distributed
> system ID of the site where the connection originated from.{color}
> {color:#172b4d}This will be used to determine internal geode communication,
> and communication between geode sites.{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-7582) Client cannot contact locator when it changes IP after restart
[ https://issues.apache.org/jira/browse/GEODE-7582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mario Ivanac resolved GEODE-7582. - Resolution: Fixed > Client cannot contact locator when it changes IP after restart > -- > > Key: GEODE-7582 > URL: https://issues.apache.org/jira/browse/GEODE-7582 > Project: Geode > Issue Type: Bug > Components: client/server >Reporter: Mario Ivanac >Assignee: Mario Ivanac >Priority: Major > Labels: needs-review, pull-request-available > Time Spent: 50m > Remaining Estimate: 0h > > Client is connected to geode multi-site system. In case locator is restarted, > and it changes IP address, client cannot contact it after. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (GEODE-7582) Client cannot contact locator when it changes IP after restart
[ https://issues.apache.org/jira/browse/GEODE-7582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mario Ivanac reopened GEODE-7582: - > Client cannot contact locator when it changes IP after restart > -- > > Key: GEODE-7582 > URL: https://issues.apache.org/jira/browse/GEODE-7582 > Project: Geode > Issue Type: Bug > Components: client/server >Reporter: Mario Ivanac >Assignee: Mario Ivanac >Priority: Major > Labels: needs-review, pull-request-available > Time Spent: 50m > Remaining Estimate: 0h > > Client is connected to geode multi-site system. In case locator is restarted, > and it changes IP address, client cannot contact it after. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-7414) SSL ClientHello server_name extension
[
https://issues.apache.org/jira/browse/GEODE-7414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mario Ivanac resolved GEODE-7414.
-
Resolution: Fixed
> SSL ClientHello server_name extension
> -
>
> Key: GEODE-7414
> URL: https://issues.apache.org/jira/browse/GEODE-7414
> Project: Geode
> Issue Type: Improvement
> Components: security
>Reporter: Mario Ivanac
>Assignee: Mario Ivanac
>Priority: Major
> Labels: needs-review, pull-request-available
> Time Spent: 1h
> Remaining Estimate: 0h
>
> {color:#172b4d}We propose to add the {color}*server_name extension to the
> ClientHello message*{color:#172b4d}. The extension would hold the distributed
> system ID of the site where the connection originated from.{color}
> {color:#172b4d}This will be used to determine internal geode communication,
> and communication between geode sites.{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-7699) when a region belongs to multiple groups, cms.get(regionA) throws an exception
Jinmei Liao created GEODE-7699: -- Summary: when a region belongs to multiple groups, cms.get(regionA) throws an exception Key: GEODE-7699 URL: https://issues.apache.org/jira/browse/GEODE-7699 Project: Geode Issue Type: Improvement Components: management Reporter: Jinmei Liao scenario: 1. create regionA in group1 2. create regionA in group2 3. do a cms.get(regionA), I would expect the result contains a list of configurations on both groups, instead, it throws an exception saying "only one is expected". -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-5816) ClusterStartupRule fails to launch JMX manager (port already in use)
[
https://issues.apache.org/jira/browse/GEODE-5816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17015235#comment-17015235
]
Darrel Schneider commented on GEODE-5816:
-
Reproduced in CI:
[https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/1473]
> ClusterStartupRule fails to launch JMX manager (port already in use)
>
>
> Key: GEODE-5816
> URL: https://issues.apache.org/jira/browse/GEODE-5816
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Bill Burcham
>Assignee: Dan Smith
>Priority: Major
> Labels: CI, swat
>
> We see these related failures on a couple tests in
> RegionMembershipMBeanOverHttpDUnitTest from our recent mass-test-run.
> From looking at the stack traces though, we surmise that the problem occurs
> in the ClusterStartupRule _before_ the actual tests run. Since it occurs
> before the tests run, we think the problem lies outside the
> RegionMembershipMBeanOverHttpDUnitTest class.
> {noformat}
> 4 failures (99.600% success
> rate)org.apache.geode.management.internal.cli.commands.RegionMembershipMBeanOverHttpDUnitTest
> | .testAddRmNewMemberWithReplicatedRegionsAndSubregions: 1 failures
> (99.900% success rate)
> | | Failed build 24 at
> https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/24
> | .testMultiplePartitionedRegions: 3 failures (99.700% success rate)
> | | Failed build 982 at
> https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/982
> | | Failed build 256 at
> https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/256
> {noformat}
> Here's a stack trace:
> {noformat}
> java.lang.AssertionError: Suspicious strings were written to the log during
> this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 358
> [error 2018/10/01 06:28:30.869 UTC
> tid=0x20] Jmx manager could not be started because
> java.rmi.server.ExportException: Port already in use: 25305; nested exception
> is:
> java.net.BindException: Failed to create server socket on
> ffd50f3577c5/172.17.0.20[25305]
> org.apache.geode.management.ManagementException:
> java.rmi.server.ExportException: Port already in use: 25305; nested exception
> is:
> java.net.BindException: Failed to create server socket on
> ffd50f3577c5/172.17.0.20[25305]
> at
> org.apache.geode.management.internal.ManagementAgent.startAgent(ManagementAgent.java:162)
> at
> org.apache.geode.management.internal.SystemManagementService.startManager(SystemManagementService.java:435)
> at
> org.apache.geode.management.internal.beans.ManagementAdapter.handleCacheCreation(ManagementAdapter.java:173)
> at
> org.apache.geode.management.internal.beans.ManagementListener.handleEvent(ManagementListener.java:118)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.notifyResourceEventListeners(InternalDistributedSystem.java:2201)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.handleResourceEvent(InternalDistributedSystem.java:591)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1218)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.basicCreate(GemFireCacheImpl.java:793)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:779)
> at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:177)
> at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:224)
> at
> org.apache.geode.distributed.internal.InternalLocator.startCache(InternalLocator.java:662)
> at
> org.apache.geode.distributed.internal.InternalLocator.startDistributedSystem(InternalLocator.java:649)
> at
> org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:311)
> at org.apache.geode.distributed.Locator.startLocator(Locator.java:253)
> at
> org.apache.geode.distributed.Locator.startLocatorAndDS(Locator.java:140)
> at
> org.apache.geode.test.junit.rules.LocatorStarterRule.startLocator(LocatorStarterRule.java:87)
> at
> org.apache.geode.test.junit.rules.LocatorStarterRule.before(LocatorStarterRule.java:68)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.lambda$startLocatorVM$22d9b8a8$1(ClusterStartupRule.java:206)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccesso
[jira] [Commented] (GEODE-5407) CI failure: JMXMBeanReconnectDUnitTest.testRemoteBeanKnowledge_MaintainServerAndCrashLocator and testLocalBeans_MaintainServerAndCrashLocator
[ https://issues.apache.org/jira/browse/GEODE-5407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17015246#comment-17015246 ] ASF subversion and git services commented on GEODE-5407: Commit 21fce819826f79e6f52adb829a5b2636a1213d9a in geode's branch refs/heads/develop from Kirk Lund [ https://gitbox.apache.org/repos/asf?p=geode.git;h=21fce81 ] GEODE-5407: Fix JMXMBeanReconnectDUnitTest * Rewrite test with standard Geode and JMX APIs * Use CountDownLatch instead of Blackboard * Use SharedErrorCollector for remote listener errors * Always consistently use Awaitility before checking GemFire MXBeans Co-authored-by: Ivan Godwin > CI failure: > JMXMBeanReconnectDUnitTest.testRemoteBeanKnowledge_MaintainServerAndCrashLocator > and testLocalBeans_MaintainServerAndCrashLocator > - > > Key: GEODE-5407 > URL: https://issues.apache.org/jira/browse/GEODE-5407 > Project: Geode > Issue Type: Bug > Components: ci, jmx, management >Reporter: Jinmei Liao >Assignee: Ivan Godwin >Priority: Major > Labels: flaky, swat > Attachments: Test results - Class > org.apache.geode.management.JMXMBeanReconnectDUnitTest.html, screenshot-1.png > > Time Spent: 3h 20m > Remaining Estimate: 0h > > org.apache.geode.management.JMXMBeanReconnectDUnitTest > > testRemoteBeanKnowledge_MaintainServerAndCrashLocator FAILED > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:249] > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.test.dunit.rules.MemberVM$$Lambda$73/2140274979.run in VM 0 > running on Host 640ab3da6905 with 4 VMs > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:250] > at org.apache.geode.test.dunit.VM.invoke(VM.java:436) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:251] > at org.apache.geode.test.dunit.VM.invoke(VM.java:405) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:252] > at org.apache.geode.test.dunit.VM.invoke(VM.java:348) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:253] > at > org.apache.geode.test.dunit.rules.MemberVM.waitTilLocatorFullyReconnected(MemberVM.java:113) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:254] > at > org.apache.geode.management.JMXMBeanReconnectDUnitTest.testRemoteBeanKnowledge_MaintainServerAndCrashLocator(JMXMBeanReconnectDUnitTest.java:161) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:255] > > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:256] > Caused by: > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:257] > org.awaitility.core.ConditionTimeoutException: Condition with > org.apache.geode.test.dunit.rules.MemberVM was not fulfilled within 30 > seconds. > > org.apache.geode.management.JMXMBeanReconnectDUnitTest > > testLocalBeans_MaintainServerAndCrashLocator FAILED > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:260] > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.test.dunit.rules.MemberVM$$Lambda$73/2140274979.run in VM 0 > running on Host 640ab3da6905 with 4 VMs > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:261] > at org.apache.geode.test.dunit.VM.invoke(VM.java:436) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:262] > at org.apache.geode.test.dunit.VM.invoke(VM.java:405) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:263] > at org.apache.geode.test.dunit.VM.invoke(VM.java:348) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:264] > at > org.apache.geode.test.dunit.rules.MemberVM.waitTilLocatorFullyReconnected(MemberVM.java:113) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:265] > at > org.apache.geode.management.JMXMBeanReconnectDUnitTest.testLocalBeans_MaintainServerAndCrashLocator(JMXMBeanReconnectDU
[jira] [Commented] (GEODE-5816) ClusterStartupRule fails to launch JMX manager (port already in use)
[
https://issues.apache.org/jira/browse/GEODE-5816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17015269#comment-17015269
]
Dan Smith commented on GEODE-5816:
--
I looked at this latest run from Darrel. It looks like it is still picking the
same port for the jmx and http services.
The PortSupplier logic that tries to prevent duplicate ports fails due to the
`locatorProperties` method I mentioned earlier, which bypasses the port
supplier. However, I'm not sure why Brian's other fix to AvailablePortHelper
itself didn't fix this problem.
> ClusterStartupRule fails to launch JMX manager (port already in use)
>
>
> Key: GEODE-5816
> URL: https://issues.apache.org/jira/browse/GEODE-5816
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Bill Burcham
>Assignee: Dan Smith
>Priority: Major
> Labels: CI, swat
>
> We see these related failures on a couple tests in
> RegionMembershipMBeanOverHttpDUnitTest from our recent mass-test-run.
> From looking at the stack traces though, we surmise that the problem occurs
> in the ClusterStartupRule _before_ the actual tests run. Since it occurs
> before the tests run, we think the problem lies outside the
> RegionMembershipMBeanOverHttpDUnitTest class.
> {noformat}
> 4 failures (99.600% success
> rate)org.apache.geode.management.internal.cli.commands.RegionMembershipMBeanOverHttpDUnitTest
> | .testAddRmNewMemberWithReplicatedRegionsAndSubregions: 1 failures
> (99.900% success rate)
> | | Failed build 24 at
> https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/24
> | .testMultiplePartitionedRegions: 3 failures (99.700% success rate)
> | | Failed build 982 at
> https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/982
> | | Failed build 256 at
> https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/256
> {noformat}
> Here's a stack trace:
> {noformat}
> java.lang.AssertionError: Suspicious strings were written to the log during
> this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 358
> [error 2018/10/01 06:28:30.869 UTC
> tid=0x20] Jmx manager could not be started because
> java.rmi.server.ExportException: Port already in use: 25305; nested exception
> is:
> java.net.BindException: Failed to create server socket on
> ffd50f3577c5/172.17.0.20[25305]
> org.apache.geode.management.ManagementException:
> java.rmi.server.ExportException: Port already in use: 25305; nested exception
> is:
> java.net.BindException: Failed to create server socket on
> ffd50f3577c5/172.17.0.20[25305]
> at
> org.apache.geode.management.internal.ManagementAgent.startAgent(ManagementAgent.java:162)
> at
> org.apache.geode.management.internal.SystemManagementService.startManager(SystemManagementService.java:435)
> at
> org.apache.geode.management.internal.beans.ManagementAdapter.handleCacheCreation(ManagementAdapter.java:173)
> at
> org.apache.geode.management.internal.beans.ManagementListener.handleEvent(ManagementListener.java:118)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.notifyResourceEventListeners(InternalDistributedSystem.java:2201)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.handleResourceEvent(InternalDistributedSystem.java:591)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1218)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.basicCreate(GemFireCacheImpl.java:793)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:779)
> at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:177)
> at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:224)
> at
> org.apache.geode.distributed.internal.InternalLocator.startCache(InternalLocator.java:662)
> at
> org.apache.geode.distributed.internal.InternalLocator.startDistributedSystem(InternalLocator.java:649)
> at
> org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:311)
> at org.apache.geode.distributed.Locator.startLocator(Locator.java:253)
> at
> org.apache.geode.distributed.Locator.startLocatorAndDS(Locator.java:140)
> at
> org.apache.geode.test.junit.rules.LocatorStarterRule.startLocator(LocatorStarterRule.java:87)
> at
> org.apache.geode.test.junit.rules.LocatorStarterRule.before(LocatorStarterRule.java:68)
> at
> or
[jira] [Commented] (GEODE-7686) User Guide: Update vMotion performance recommendations
[ https://issues.apache.org/jira/browse/GEODE-7686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17015325#comment-17015325 ] ASF subversion and git services commented on GEODE-7686: Commit ec4fb9e303cdf45cef87d4bb44d77f37e38c2b6d in geode's branch refs/heads/develop from Dave Barnes [ https://gitbox.apache.org/repos/asf?p=geode.git;h=ec4fb9e ] GEODE-7686: Update the vMotion recommendations in the User Guide (#4582) * GEODE-7686: Update the vMotion recommendations in the User Guide based on recent understandings. > User Guide: Update vMotion performance recommendations > -- > > Key: GEODE-7686 > URL: https://issues.apache.org/jira/browse/GEODE-7686 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > Update the vMotion recommendations in the User Guide based on recent > understandings. > [https://geode.apache.org/docs/guide/111/managing/monitor_tune/performance_on_vsphere.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7686) User Guide: Update vMotion performance recommendations
[ https://issues.apache.org/jira/browse/GEODE-7686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17015324#comment-17015324 ] ASF subversion and git services commented on GEODE-7686: Commit ec4fb9e303cdf45cef87d4bb44d77f37e38c2b6d in geode's branch refs/heads/develop from Dave Barnes [ https://gitbox.apache.org/repos/asf?p=geode.git;h=ec4fb9e ] GEODE-7686: Update the vMotion recommendations in the User Guide (#4582) * GEODE-7686: Update the vMotion recommendations in the User Guide based on recent understandings. > User Guide: Update vMotion performance recommendations > -- > > Key: GEODE-7686 > URL: https://issues.apache.org/jira/browse/GEODE-7686 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > Update the vMotion recommendations in the User Guide based on recent > understandings. > [https://geode.apache.org/docs/guide/111/managing/monitor_tune/performance_on_vsphere.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-7686) User Guide: Update vMotion performance recommendations
[ https://issues.apache.org/jira/browse/GEODE-7686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-7686. Fix Version/s: 1.11.0 Resolution: Fixed > User Guide: Update vMotion performance recommendations > -- > > Key: GEODE-7686 > URL: https://issues.apache.org/jira/browse/GEODE-7686 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Fix For: 1.11.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Update the vMotion recommendations in the User Guide based on recent > understandings. > [https://geode.apache.org/docs/guide/111/managing/monitor_tune/performance_on_vsphere.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-5407) CI failure: JMXMBeanReconnectDUnitTest.testRemoteBeanKnowledge_MaintainServerAndCrashLocator and testLocalBeans_MaintainServerAndCrashLocator
[ https://issues.apache.org/jira/browse/GEODE-5407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Godwin resolved GEODE-5407. Resolution: Fixed > CI failure: > JMXMBeanReconnectDUnitTest.testRemoteBeanKnowledge_MaintainServerAndCrashLocator > and testLocalBeans_MaintainServerAndCrashLocator > - > > Key: GEODE-5407 > URL: https://issues.apache.org/jira/browse/GEODE-5407 > Project: Geode > Issue Type: Bug > Components: ci, jmx, management >Reporter: Jinmei Liao >Assignee: Ivan Godwin >Priority: Major > Labels: flaky, swat > Attachments: Test results - Class > org.apache.geode.management.JMXMBeanReconnectDUnitTest.html, screenshot-1.png > > Time Spent: 3h 20m > Remaining Estimate: 0h > > org.apache.geode.management.JMXMBeanReconnectDUnitTest > > testRemoteBeanKnowledge_MaintainServerAndCrashLocator FAILED > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:249] > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.test.dunit.rules.MemberVM$$Lambda$73/2140274979.run in VM 0 > running on Host 640ab3da6905 with 4 VMs > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:250] > at org.apache.geode.test.dunit.VM.invoke(VM.java:436) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:251] > at org.apache.geode.test.dunit.VM.invoke(VM.java:405) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:252] > at org.apache.geode.test.dunit.VM.invoke(VM.java:348) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:253] > at > org.apache.geode.test.dunit.rules.MemberVM.waitTilLocatorFullyReconnected(MemberVM.java:113) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:254] > at > org.apache.geode.management.JMXMBeanReconnectDUnitTest.testRemoteBeanKnowledge_MaintainServerAndCrashLocator(JMXMBeanReconnectDUnitTest.java:161) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:255] > > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:256] > Caused by: > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:257] > org.awaitility.core.ConditionTimeoutException: Condition with > org.apache.geode.test.dunit.rules.MemberVM was not fulfilled within 30 > seconds. > > org.apache.geode.management.JMXMBeanReconnectDUnitTest > > testLocalBeans_MaintainServerAndCrashLocator FAILED > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:260] > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.test.dunit.rules.MemberVM$$Lambda$73/2140274979.run in VM 0 > running on Host 640ab3da6905 with 4 VMs > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:261] > at org.apache.geode.test.dunit.VM.invoke(VM.java:436) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:262] > at org.apache.geode.test.dunit.VM.invoke(VM.java:405) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:263] > at org.apache.geode.test.dunit.VM.invoke(VM.java:348) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:264] > at > org.apache.geode.test.dunit.rules.MemberVM.waitTilLocatorFullyReconnected(MemberVM.java:113) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:265] > at > org.apache.geode.management.JMXMBeanReconnectDUnitTest.testLocalBeans_MaintainServerAndCrashLocator(JMXMBeanReconnectDUnitTest.java:112) > > Caused by: > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/103#L5b401925:268] > org.awaitility.core.ConditionTimeoutException: Condition with > org.apache.geode.test.dunit.rules.MemberVM was not fulfilled within 30 > seconds. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-7517) JMXMBeanReconnectDUnitTest.testLocalBeans_MaintainServerAndCrashLocator
[
https://issues.apache.org/jira/browse/GEODE-7517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Godwin resolved GEODE-7517.
Resolution: Fixed
Fixed with following commit:
Commit 21fce819826f79e6f52adb829a5b2636a1213d9a in geode's branch
refs/heads/develop from Kirk Lund
[ [https://gitbox.apache.org/repos/asf?p=geode.git;h=21fce81] ]
GEODE-5407: Fix JMXMBeanReconnectDUnitTest
* Rewrite test with standard Geode and JMX APIs
* Use CountDownLatch instead of Blackboard
* Use SharedErrorCollector for remote listener errors
* Always consistently use Awaitility before checking GemFire MXBeans
Co-authored-by: Ivan Godwin
> JMXMBeanReconnectDUnitTest.testLocalBeans_MaintainServerAndCrashLocator
> ---
>
> Key: GEODE-7517
> URL: https://issues.apache.org/jira/browse/GEODE-7517
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Mark Hanson
>Assignee: Ivan Godwin
>Priority: Major
> Labels: flaky
>
> Failures found during mass test runs.
> {noformat}
> testLocalBeans_MaintainServerAndCrashLocator
> https://concourse.apachegeode-ci.info/teams/main/pipelines/mhansonp-mhanson-mass-test-ru-main/jobs/DistributedTestOpenJDK8/builds/1940
> testLocalBeans_MaintainServerAndCrashLocator
> https://concourse.apachegeode-ci.info/teams/main/pipelines/mhansonp-mhanson-mass-test-ru-main/jobs/DistributedTestOpenJDK8/builds/1845
> {noformat}
> Stack trace from 1940 run
> {noformat}
> org.awaitility.core.ConditionTimeoutException: Condition with alias 'Locators
> must agree on the state of the system' didn't complete within 300 seconds
> because assertion condition defined as a lambda expression in
> org.apache.geode.management.JMXMBeanReconnectDUnitTest
> Expecting:
> <[GemFire:service=Region,name="/test-region-1",type=Distributed,
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Distributed,
> GemFire:service=AccessControl,type=Distributed,
> GemFire:service=FileUploader,type=Distributed,
> GemFire:service=System,type=Distributed,
>
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator-0,
>
> GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator-0,
> GemFire:service=Locator,type=Member,member=locator-0,
> GemFire:type=Member,member=locator-0,
>
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator-1,
>
> GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator-1,
> GemFire:service=Locator,type=Member,member=locator-1,
> GemFire:type=Member,member=locator-1,
> GemFire:service=Region,name="/test-region-1",type=Member,member=server-2,
> GemFire:service=CacheServer,port=42991,type=Member,member=server-2,
> GemFire:type=Member,member=server-2,
> GemFire:service=Region,name="/test-region-1",type=Member,member=server-3,
> GemFire:service=CacheServer,port=41287,type=Member,member=server-3,
> GemFire:type=Member,member=server-3]>
> to contain exactly (and in same order):
> <[GemFire:service=Region,name="/test-region-1",type=Distributed,
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Distributed,
> GemFire:service=AccessControl,type=Distributed,
> GemFire:service=FileUploader,type=Distributed,
> GemFire:service=System,type=Distributed,
> GemFire:service=Locator,type=Member,member=locator-0,
> GemFire:type=Member,member=locator-0,
>
> GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator-1,
>
> GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator-1,
> GemFire:service=Locator,type=Member,member=locator-1,
> GemFire:type=Member,member=locator-1,
> GemFire:service=Region,name="/test-region-1",type=Member,member=server-2,
> GemFire:service=CacheServer,port=42991,type=Member,member=server-2,
> GemFire:type=Member,member=server-2,
> GemFire:service=Region,name="/test-region-1",type=Member,member=server-3,
> GemFire:service=CacheServer,port=41287,type=Member,member=server-3,
> GemFire:type=Member,member=server-3]>
> but some elements were not expected:
>
> <[GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator-0,
>
> GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator-0]>
> .
> at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:145)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:122)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32)
> at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:902)
> at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory
[jira] [Resolved] (GEODE-7687) User Guide: Remove time-based statistics caveat
[ https://issues.apache.org/jira/browse/GEODE-7687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-7687. Fix Version/s: 1.11.0 Resolution: Fixed > User Guide: Remove time-based statistics caveat > --- > > Key: GEODE-7687 > URL: https://issues.apache.org/jira/browse/GEODE-7687 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Fix For: 1.11.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The User Guide advises against enabling time-based statistics in production > environments. As of Geode v1.9, this limitation is no longer significant, so > the warning against it should be removed from the user guide. > [https://geode.apache.org/docs/guide/111/managing/statistics/how_statistics_work.html] > [https://geode.apache.org/docs/guide/111/managing/statistics/setting_up_statistics.html] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-6819) CI failure: PartitionedRegionSingleHopDUnitTest. testMetadataIsSameOnAllServersAndClients
[
https://issues.apache.org/jira/browse/GEODE-6819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Godwin reassigned GEODE-6819:
--
Assignee: Ivan Godwin
> CI failure: PartitionedRegionSingleHopDUnitTest.
> testMetadataIsSameOnAllServersAndClients
> -
>
> Key: GEODE-6819
> URL: https://issues.apache.org/jira/browse/GEODE-6819
> Project: Geode
> Issue Type: Bug
> Components: client/server
>Reporter: Bruce J Schuchardt
>Assignee: Ivan Godwin
>Priority: Major
> Labels: flaky
>
> {noformat}
> org.apache.geode.internal.cache.PartitionedRegionSingleHopDUnitTest >
> testMetadataIsSameOnAllServersAndClients FAILED
> org.awaitility.core.ConditionTimeoutException: Assertion condition
> defined in public void
> org.apache.geode.internal.cache.PartitionedRegionSingleHopDUnitTest.testMetadataIsSameOnAllServersAndClients()
> bucket copies are not created within 300 seconds.
> at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:145)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:122)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:902)
> at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:723)
> at
> org.apache.geode.internal.cache.PartitionedRegionSingleHopDUnitTest.testMetadataIsSameOnAllServersAndClients(PartitionedRegionSingleHopDUnitTest.java:849)
> Caused by:
> java.lang.AssertionError: bucket copies are not created{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-7116) CI Failure: PartitionedRegionSingleHopDUnitTest > testServerLocationRemovalThroughPing
[ https://issues.apache.org/jira/browse/GEODE-7116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Godwin reassigned GEODE-7116: -- Assignee: Ivan Godwin > CI Failure: PartitionedRegionSingleHopDUnitTest > > testServerLocationRemovalThroughPing > -- > > Key: GEODE-7116 > URL: https://issues.apache.org/jira/browse/GEODE-7116 > Project: Geode > Issue Type: Bug >Reporter: Donal Evans >Assignee: Ivan Godwin >Priority: Major > Labels: flaky > > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/1008 > org.apache.geode.internal.cache.PartitionedRegionSingleHopDUnitTest > > testServerLocationRemovalThroughPing FAILED > java.lang.AssertionError: expected:<4> but was:<0> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:834) > at org.junit.Assert.assertEquals(Assert.java:645) > at org.junit.Assert.assertEquals(Assert.java:631) > at > org.apache.geode.internal.cache.PartitionedRegionSingleHopDUnitTest.testServerLocationRemovalThroughPing(PartitionedRegionSingleHopDUnitTest.java:679) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7693) Equals method should compare same object types as parameters
[ https://issues.apache.org/jira/browse/GEODE-7693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17015413#comment-17015413 ] ASF subversion and git services commented on GEODE-7693: Commit 5f6d45104536b58e6593e5e91424713a9ea20448 in geode's branch refs/heads/develop from Nabarun Nag [ https://gitbox.apache.org/repos/asf?p=geode.git;h=5f6d451 ] GEODE-7693: Equals compares objects of same type (#4589) > Equals method should compare same object types as parameters > > > Key: GEODE-7693 > URL: https://issues.apache.org/jira/browse/GEODE-7693 > Project: Geode > Issue Type: Bug >Reporter: Nabarun Nag >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7605) PersistentRecoveryOrderDUnitTest and PersistentRecoveryOrderOldConfigDUnitTest fail in testGIIDuringDestroy
[
https://issues.apache.org/jira/browse/GEODE-7605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17015424#comment-17015424
]
ASF subversion and git services commented on GEODE-7605:
Commit 274504bef0243bc93cf9cb3d19d75a58d00630a4 in geode's branch
refs/heads/develop from Kirk Lund
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=274504b ]
GEODE-7605: Fix PersistentRecoveryOrderDUnitTest (#4591)
Ignore RegionDestroyedException while waiting for region to be
destroyed.
> PersistentRecoveryOrderDUnitTest and
> PersistentRecoveryOrderOldConfigDUnitTest fail in testGIIDuringDestroy
> ---
>
> Key: GEODE-7605
> URL: https://issues.apache.org/jira/browse/GEODE-7605
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Mark Hanson
>Assignee: Kirk Lund
>Priority: Major
> Labels: flaky
> Time Spent: 20m
> Remaining Estimate: 0h
>
> org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderDUnitTest:
> 1 failures (99.667% success rate)
> testGIIDuringDestroy
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/mhansonp-mhanson-mass-test-ru-main/jobs/DistributedTestOpenJDK8/builds/2251]
> {noformat}
> 01:38:05org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderDUnitTest
> > testGIIDuringDestroy FAILED
> 01:38:05org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderDUnitTest$$Lambda$196/1137975618.run
> in VM 1 running on Host c27ac1dbf5cd with 4 VMs
> 01:38:05at
> org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)
> 01:38:05at org.apache.geode.test.dunit.VM.invoke(VM.java:437)
> 01:38:05at
> org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderDUnitTest.testGIIDuringDestroy(PersistentRecoveryOrderDUnitTest.java:1004)
> 01:38:05
> 01:38:05Caused by:
> 01:38:05org.apache.geode.cache.RegionDestroyedException:
> org.apache.geode.internal.cache.DistributedRegion[path='/PersistentRecoveryOrderDUnitTest_testGIIDuringDestroyRegion';scope=DISTRIBUTED_ACK';dataPolicy=PERSISTENT_REPLICATE;
> concurrencyChecksEnabled]
> 01:38:05at
> org.apache.geode.internal.cache.LocalRegion.checkRegionDestroyed(LocalRegion.java:7296)
> 01:38:05at
> org.apache.geode.internal.cache.LocalRegion.checkReadiness(LocalRegion.java:2750)
> 01:38:05at
> org.apache.geode.internal.cache.LocalRegion.size(LocalRegion.java:8256)
> 01:38:05at java.util.TreeMap.putAll(TreeMap.java:313)
> 01:38:05at java.util.TreeMap.(TreeMap.java:185)
> 01:38:05at
> org.assertj.core.presentation.StandardRepresentation.toSortedMapIfPossible(StandardRepresentation.java:339)
> 01:38:05at
> org.assertj.core.presentation.StandardRepresentation.toStringOf(StandardRepresentation.java:319)
> 01:38:05at
> org.assertj.core.presentation.StandardRepresentation.toStringOf(StandardRepresentation.java:178)
> 01:38:05at
> org.assertj.core.error.ShouldBeEqual.actualAndExpectedHaveSameStringRepresentation(ShouldBeEqual.java:137)
> 01:38:05at
> org.assertj.core.error.ShouldBeEqual.smartErrorMessage(ShouldBeEqual.java:151)
> 01:38:05at
> org.assertj.core.error.ShouldBeEqual.newAssertionError(ShouldBeEqual.java:116)
> 01:38:05at
> org.assertj.core.internal.Failures.failure(Failures.java:100)
> 01:38:05at
> org.assertj.core.internal.Objects.assertNull(Objects.java:364)
> 01:38:05at
> org.assertj.core.api.AbstractAssert.isNull(AbstractAssert.java:272)
> 01:38:05at
> org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderDUnitTest.lambda$null$16(PersistentRecoveryOrderDUnitTest.java:1007)
> 01:38:05
> 01:38:05java.lang.AssertionError: Suspicious strings were written to the
> log during this run.
> 01:38:05Fix the strings or use IgnoredException.addIgnoredException to
> ignore.
> 01:38:05
> ---
> 01:38:05Found suspect string in log4j at line 1923
> 01:38:05
> 01:38:05[error 2019/12/19 09:38:03.305 GMT Connection(1)-172.17.0.3> tid=32]
> org.apache.geode.distributed.DistributedSystemDisconnectedException: This
> connection to a distributed system has been disconnected.
> 02:22:02 {noformat}
> org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderOldConfigDUnitTest:
> 1 failures (99.667% success rate)
> testGIIDuringDestroy
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/mhansonp-mhanson-mass-test-ru-main/jobs/DistributedTestOpenJDK8/builds/2212]
>
> {n
[jira] [Resolved] (GEODE-7605) PersistentRecoveryOrderDUnitTest and PersistentRecoveryOrderOldConfigDUnitTest fail in testGIIDuringDestroy
[
https://issues.apache.org/jira/browse/GEODE-7605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund resolved GEODE-7605.
--
Fix Version/s: 1.12.0
Resolution: Fixed
> PersistentRecoveryOrderDUnitTest and
> PersistentRecoveryOrderOldConfigDUnitTest fail in testGIIDuringDestroy
> ---
>
> Key: GEODE-7605
> URL: https://issues.apache.org/jira/browse/GEODE-7605
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Mark Hanson
>Assignee: Kirk Lund
>Priority: Major
> Labels: flaky
> Fix For: 1.12.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderDUnitTest:
> 1 failures (99.667% success rate)
> testGIIDuringDestroy
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/mhansonp-mhanson-mass-test-ru-main/jobs/DistributedTestOpenJDK8/builds/2251]
> {noformat}
> 01:38:05org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderDUnitTest
> > testGIIDuringDestroy FAILED
> 01:38:05org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderDUnitTest$$Lambda$196/1137975618.run
> in VM 1 running on Host c27ac1dbf5cd with 4 VMs
> 01:38:05at
> org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)
> 01:38:05at org.apache.geode.test.dunit.VM.invoke(VM.java:437)
> 01:38:05at
> org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderDUnitTest.testGIIDuringDestroy(PersistentRecoveryOrderDUnitTest.java:1004)
> 01:38:05
> 01:38:05Caused by:
> 01:38:05org.apache.geode.cache.RegionDestroyedException:
> org.apache.geode.internal.cache.DistributedRegion[path='/PersistentRecoveryOrderDUnitTest_testGIIDuringDestroyRegion';scope=DISTRIBUTED_ACK';dataPolicy=PERSISTENT_REPLICATE;
> concurrencyChecksEnabled]
> 01:38:05at
> org.apache.geode.internal.cache.LocalRegion.checkRegionDestroyed(LocalRegion.java:7296)
> 01:38:05at
> org.apache.geode.internal.cache.LocalRegion.checkReadiness(LocalRegion.java:2750)
> 01:38:05at
> org.apache.geode.internal.cache.LocalRegion.size(LocalRegion.java:8256)
> 01:38:05at java.util.TreeMap.putAll(TreeMap.java:313)
> 01:38:05at java.util.TreeMap.(TreeMap.java:185)
> 01:38:05at
> org.assertj.core.presentation.StandardRepresentation.toSortedMapIfPossible(StandardRepresentation.java:339)
> 01:38:05at
> org.assertj.core.presentation.StandardRepresentation.toStringOf(StandardRepresentation.java:319)
> 01:38:05at
> org.assertj.core.presentation.StandardRepresentation.toStringOf(StandardRepresentation.java:178)
> 01:38:05at
> org.assertj.core.error.ShouldBeEqual.actualAndExpectedHaveSameStringRepresentation(ShouldBeEqual.java:137)
> 01:38:05at
> org.assertj.core.error.ShouldBeEqual.smartErrorMessage(ShouldBeEqual.java:151)
> 01:38:05at
> org.assertj.core.error.ShouldBeEqual.newAssertionError(ShouldBeEqual.java:116)
> 01:38:05at
> org.assertj.core.internal.Failures.failure(Failures.java:100)
> 01:38:05at
> org.assertj.core.internal.Objects.assertNull(Objects.java:364)
> 01:38:05at
> org.assertj.core.api.AbstractAssert.isNull(AbstractAssert.java:272)
> 01:38:05at
> org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderDUnitTest.lambda$null$16(PersistentRecoveryOrderDUnitTest.java:1007)
> 01:38:05
> 01:38:05java.lang.AssertionError: Suspicious strings were written to the
> log during this run.
> 01:38:05Fix the strings or use IgnoredException.addIgnoredException to
> ignore.
> 01:38:05
> ---
> 01:38:05Found suspect string in log4j at line 1923
> 01:38:05
> 01:38:05[error 2019/12/19 09:38:03.305 GMT Connection(1)-172.17.0.3> tid=32]
> org.apache.geode.distributed.DistributedSystemDisconnectedException: This
> connection to a distributed system has been disconnected.
> 02:22:02 {noformat}
> org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderOldConfigDUnitTest:
> 1 failures (99.667% success rate)
> testGIIDuringDestroy
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/mhansonp-mhanson-mass-test-ru-main/jobs/DistributedTestOpenJDK8/builds/2212]
>
> {noformat}
> org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderOldConfigDUnitTest
> > testGIIDuringDestroy FAILED
> 09:18:39org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderDUnitTest$$Lambda$196/873195048.run
> in
[jira] [Assigned] (GEODE-7604) QueryConfigurationServiceConstraintsDistributedTest
[
https://issues.apache.org/jira/browse/GEODE-7604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund reassigned GEODE-7604:
Assignee: Kirk Lund
> QueryConfigurationServiceConstraintsDistributedTest
> ---
>
> Key: GEODE-7604
> URL: https://issues.apache.org/jira/browse/GEODE-7604
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Mark Hanson
>Assignee: Kirk Lund
>Priority: Major
> Labels: flaky
>
> QueryConfigurationServiceConstraintsDistributedTest had two failures in the
> mass test run...
> [2]
> https://concourse.apachegeode-ci.info/teams/main/pipelines/mhansonp-mhanson-mass-test-ru-main/jobs/DistributedTestOpenJDK8/builds/2252
> [6]
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/mhansonp-mhanson-mass-test-ru-main/jobs/DistributedTestOpenJDK8/builds/2211]
>
> {noformat}
> 01:28:56org.apache.geode.cache.query.internal.QueryConfigurationServiceConstraintsDistributedTest
> > [2]
> cqsShouldSucceedDuringEventProcessingAfterRegionOperationWhenMethodAuthorizerIsChangedAndQueryContainsMethodsAllowedByTheNewAuthorizer(RegionType:REPLICATE;Operation:CREATE,ExecuteWithInitialResults:true)
> FAILED
> 01:28:56org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache.query.internal.QueryConfigurationServiceConstraintsDistributedTest$$Lambda$57/2082907347.run
> in VM 2 running on Host 8cbcba2ac2b2 with 4 VMs
> 01:28:56at
> org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)
> 01:28:56at org.apache.geode.test.dunit.VM.invoke(VM.java:437)
> 01:28:56at
> org.apache.geode.test.junit.rules.VMProvider.invoke(VMProvider.java:94)
> 01:28:56at
> org.apache.geode.cache.query.internal.QueryConfigurationServiceConstraintsDistributedTest.cqsShouldSucceedDuringEventProcessingAfterRegionOperationWhenMethodAuthorizerIsChangedAndQueryContainsMethodsAllowedByTheNewAuthorizer(QueryConfigurationServiceConstraintsDistributedTest.java:260)
> 01:28:56
> 01:28:56Caused by:
> 01:28:56org.awaitility.core.ConditionTimeoutException: Assertion
> condition defined as a
> org.apache.geode.cache.query.internal.QueryConfigurationServiceConstraintsDistributedTest
> expected:<[7]> but was:<[4]> within 300 seconds.
> 01:28:56at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:145)
> 01:28:56at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:122)
> 01:28:56at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32)
> 01:28:56at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:902)
> 01:28:56at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:723)
> 01:28:56at
> org.apache.geode.cache.query.internal.QueryConfigurationServiceConstraintsDistributedTest.lambda$cqsShouldSucceedDuringEventProcessingAfterRegionOperationWhenMethodAuthorizerIsChangedAndQueryContainsMethodsAllowedByTheNewAuthorizer$868d1d80$1(QueryConfigurationServiceConstraintsDistributedTest.java:264)
> 01:28:56
> 01:28:56Caused by:
> 01:28:56org.junit.ComparisonFailure: expected:<[7]> but was:<[4]>
> 01:28:56at
> sun.reflect.GeneratedConstructorAccessor207.newInstance(Unknown Source)
> 01:28:56at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> 01:28:56at
> org.apache.geode.cache.query.internal.QueryConfigurationServiceConstraintsDistributedTest.lambda$null$13(QueryConfigurationServiceConstraintsDistributedTest.java:266)
> 02:03:51
> 02:03:51679 tests completed, 1 failed, 39 skipped {noformat}
>
>
> {noformat}
> 07:59:46org.apache.geode.cache.query.internal.QueryConfigurationServiceConstraintsDistributedTest
> > [6]
> cqsShouldFailDuringEventProcessingAfterRegionOperationWhenMethodAuthorizerIsChangedAndQueryContainsMethodsNotAllowedByTheNewAuthorizer(RegionType:REPLICATE;Operation:DESTROY,ExecuteWithInitialResults:true)
> FAILED
> 07:59:46org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache.query.internal.QueryConfigurationServiceConstraintsDistributedTest$$Lambda$33/1244479648.run
> in VM 2 running on Host 4f921f4602aa with 4 VMs
> 07:59:46at
> org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)
> 07:59:46at org.apache.geode.test.dunit.VM.invoke(VM.java:437)
> 07:59:46at
> org.apache.geode.test.junit.rules.VMProvider.invoke(VMProvider.java:94)
> 07:59:46at
> org.apache.geode.cache.query.internal.QueryConfigurationServiceConstraintsDistributedTest.cqsShouldFailDuringEventProcessingAfterRegionOperationWhenMethodAuthorizerIsChangedAnd
[jira] [Created] (GEODE-7700) AbstractExecutorGroupJUnitTest lockOwnerThreadStackIsReported failing intermittently
Darrel Schneider created GEODE-7700:
---
Summary: AbstractExecutorGroupJUnitTest
lockOwnerThreadStackIsReported failing intermittently
Key: GEODE-7700
URL: https://issues.apache.org/jira/browse/GEODE-7700
Project: Geode
Issue Type: Bug
Components: core
Reporter: Darrel Schneider
see:
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsUnitTestOpenJDK11/builds/1221
{noformat}
org.apache.geode.internal.monitoring.executor.AbstractExecutorGroupJUnitTest >
lockOwnerThreadStackIsReported FAILED
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertTrue(Assert.java:52)
at
org.apache.geode.internal.monitoring.executor.AbstractExecutorGroupJUnitTest.lockOwnerThreadStackIsReported(AbstractExecutorGroupJUnitTest.java:99)
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-7700) AbstractExecutorGroupJUnitTest lockOwnerThreadStackIsReported failing intermittently
[
https://issues.apache.org/jira/browse/GEODE-7700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darrel Schneider reassigned GEODE-7700:
---
Assignee: Bruce J Schuchardt
> AbstractExecutorGroupJUnitTest lockOwnerThreadStackIsReported failing
> intermittently
>
>
> Key: GEODE-7700
> URL: https://issues.apache.org/jira/browse/GEODE-7700
> Project: Geode
> Issue Type: Bug
> Components: core
>Reporter: Darrel Schneider
>Assignee: Bruce J Schuchardt
>Priority: Major
>
> see:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsUnitTestOpenJDK11/builds/1221
> {noformat}
> org.apache.geode.internal.monitoring.executor.AbstractExecutorGroupJUnitTest
> > lockOwnerThreadStackIsReported FAILED
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertTrue(Assert.java:52)
> at
> org.apache.geode.internal.monitoring.executor.AbstractExecutorGroupJUnitTest.lockOwnerThreadStackIsReported(AbstractExecutorGroupJUnitTest.java:99)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-7700) AbstractExecutorGroupJUnitTest lockOwnerThreadStackIsReported failing intermittently
[
https://issues.apache.org/jira/browse/GEODE-7700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darrel Schneider updated GEODE-7700:
Labels: flaky (was: )
> AbstractExecutorGroupJUnitTest lockOwnerThreadStackIsReported failing
> intermittently
>
>
> Key: GEODE-7700
> URL: https://issues.apache.org/jira/browse/GEODE-7700
> Project: Geode
> Issue Type: Bug
> Components: core
>Reporter: Darrel Schneider
>Assignee: Bruce J Schuchardt
>Priority: Major
> Labels: flaky
>
> see:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsUnitTestOpenJDK11/builds/1221
> {noformat}
> org.apache.geode.internal.monitoring.executor.AbstractExecutorGroupJUnitTest
> > lockOwnerThreadStackIsReported FAILED
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertTrue(Assert.java:52)
> at
> org.apache.geode.internal.monitoring.executor.AbstractExecutorGroupJUnitTest.lockOwnerThreadStackIsReported(AbstractExecutorGroupJUnitTest.java:99)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-7559) LGTM Container Contents never accessed TXOriginatorRecoveryProcessor.java
[ https://issues.apache.org/jira/browse/GEODE-7559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Oleske reassigned GEODE-7559: - Assignee: Michael Oleske > LGTM Container Contents never accessed TXOriginatorRecoveryProcessor.java > - > > Key: GEODE-7559 > URL: https://issues.apache.org/jira/browse/GEODE-7559 > Project: Geode > Issue Type: Improvement >Reporter: Michael Oleske >Assignee: Michael Oleske >Priority: Major > Time Spent: 1.5h > Remaining Estimate: 0h > > https://lgtm.com/projects/g/apache/geode/snapshot/34f63b2c4d9c643a4c099ce7e1bf544d3f51e719/files/geode-core/src/main/java/org/apache/geode/internal/cache/locks/TXOriginatorRecoveryProcessor.java?sort=name&dir=ASC&mode=heatmap#V61 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-7559) LGTM Container Contents never accessed TXOriginatorRecoveryProcessor.java
[ https://issues.apache.org/jira/browse/GEODE-7559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Oleske resolved GEODE-7559. --- Resolution: Duplicate duplicate of GEODE-7689 > LGTM Container Contents never accessed TXOriginatorRecoveryProcessor.java > - > > Key: GEODE-7559 > URL: https://issues.apache.org/jira/browse/GEODE-7559 > Project: Geode > Issue Type: Improvement >Reporter: Michael Oleske >Priority: Major > Time Spent: 1.5h > Remaining Estimate: 0h > > https://lgtm.com/projects/g/apache/geode/snapshot/34f63b2c4d9c643a4c099ce7e1bf544d3f51e719/files/geode-core/src/main/java/org/apache/geode/internal/cache/locks/TXOriginatorRecoveryProcessor.java?sort=name&dir=ASC&mode=heatmap#V61 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7700) AbstractExecutorGroupJUnitTest lockOwnerThreadStackIsReported failing intermittently
[
https://issues.apache.org/jira/browse/GEODE-7700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce J Schuchardt updated GEODE-7700:
--
Component/s: membership
> AbstractExecutorGroupJUnitTest lockOwnerThreadStackIsReported failing
> intermittently
>
>
> Key: GEODE-7700
> URL: https://issues.apache.org/jira/browse/GEODE-7700
> Project: Geode
> Issue Type: Bug
> Components: core, membership
>Reporter: Darrel Schneider
>Assignee: Bruce J Schuchardt
>Priority: Major
> Labels: flaky
>
> see:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsUnitTestOpenJDK11/builds/1221
> {noformat}
> org.apache.geode.internal.monitoring.executor.AbstractExecutorGroupJUnitTest
> > lockOwnerThreadStackIsReported FAILED
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertTrue(Assert.java:52)
> at
> org.apache.geode.internal.monitoring.executor.AbstractExecutorGroupJUnitTest.lockOwnerThreadStackIsReported(AbstractExecutorGroupJUnitTest.java:99)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-6833) p2p SSL connections always require clients to authenticate
[
https://issues.apache.org/jira/browse/GEODE-6833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17015541#comment-17015541
]
ASF subversion and git services commented on GEODE-6833:
Commit 779e5ce0fe4630534fa598e40b17e5e84cb188b3 in geode's branch
refs/heads/develop from Bill Burcham
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=779e5ce ]
GEODE-6833: remove redundant ArchRule and layer spec (#4594)
> p2p SSL connections always require clients to authenticate
> --
>
> Key: GEODE-6833
> URL: https://issues.apache.org/jira/browse/GEODE-6833
> Project: Geode
> Issue Type: Bug
> Components: core
>Reporter: Bruce J Schuchardt
>Assignee: Ernest Burghardt
>Priority: Major
> Fix For: 1.10.0
>
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
> The SSL over NIO code is configuring the SSL engine to always require a
> connection to do two-way authentication. Connection.createIoFilter() is
> currently doing this:
> {code:java}
> if (!clientSocket) {
> engine.setWantClientAuth(true);
> engine.setNeedClientAuth(true);
> }
> {code}
> but needs to do this instead:
> {code:java}
> if (!clientSocket) {
>
> engine.setNeedClientAuth(SSLConfigurationFactory.getSSLConfigForComponent(getConduit().config,
> SecurableCommunicationChannel.CLUSTER).isRequireAuth());
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
