[jira] [Commented] (GEODE-9340) Benchmark instability in PartitionedPutLongBenchmark

2021-08-21 Thread Geode Integration (Jira)

[ 
https://issues.apache.org/jira/browse/GEODE-9340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17402728#comment-17402728
 ] 

Geode Integration commented on GEODE-9340:
--

Seen in [benchmark-base 
#136|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/benchmark-base/builds/136].

> Benchmark instability in PartitionedPutLongBenchmark
> 
>
> Key: GEODE-9340
> URL: https://issues.apache.org/jira/browse/GEODE-9340
> Project: Geode
>  Issue Type: Bug
>  Components: benchmarks
>Affects Versions: 1.15.0
>Reporter: Sarah Abbey
>Assignee: Hale Bales
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.13.3, 1.13.4, 1.14.0, 1.15.0
>
>
> PartitionedPutLongBenchmark failed in CI 
> (https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/benchmark-base/builds/6):
> {code:java}
> This is ITERATION 1 of benchmarking against baseline.
>   P2pPartitionedGetBenchmark avg ops/sec  
> Baseline:825011.38  Test:835847.67  Difference:   +1.3%
>  avg latency  
> Baseline:871392.31  Test:859444.66  Difference:   -1.4%
>   P2pPartitionedPutBenchmark avg ops/sec  
> Baseline:123838.43  Test:122686.30  Difference:   -0.9%
>  avg latency  
> Baseline:   6015719.73  Test:   6119472.19  Difference:   +1.7%
>  P2pPartitionedPutBytesBenchmark avg ops/sec  
> Baseline:174887.77  Test:171040.93  Difference:   -2.2%
>  avg latency  
> Baseline:   4145337.60  Test:   4236159.60  Difference:   +2.2%
>    PartitionedFunctionExecutionBenchmark avg ops/sec  
> Baseline:248635.36  Test:261498.94  Difference:   +5.2%
>  avg latency  
> Baseline:867122.63  Test:824550.34  Difference:   -4.9%
>   PartitionedFunctionExecutionWithArgumentsBenchmark avg ops/sec  
> Baseline:280071.19  Test:275305.31  Difference:   -1.7%
>  avg latency  
> Baseline:   1026643.12  Test:   1044307.43  Difference:   +1.7%
> PartitionedFunctionExecutionWithFiltersBenchmark avg ops/sec  
> Baseline:301416.23  Test:304317.30  Difference:   +1.0%
>  avg latency  
> Baseline:   1908390.88  Test:   1890040.46  Difference:   -1.0%
>  PartitionedGetBenchmark avg ops/sec  
> Baseline:790800.52  Test:784514.74  Difference:   -0.8%
>  avg latency  
> Baseline:908357.58  Test:915790.96  Difference:   +0.8%
>  PartitionedGetLongBenchmark avg ops/sec  
> Baseline:   1020821.32  Test:996529.93  Difference:   -2.4%
>  avg latency  
> Baseline:703761.09  Test:720744.36  Difference:   +2.4%
>    PartitionedGetStringBenchmark avg ops/sec  
> Baseline:   1028992.93  Test:   1010447.47  Difference:   -1.8%
>  avg latency  
> Baseline:698009.55  Test:710765.29  Difference:   +1.8%
> PartitionedIndexedQueryBenchmark avg ops/sec  
> Baseline: 30868.78  Test: 31478.90  Difference:   +2.0%
>  avg latency  
> Baseline:  18670093.21  Test:  18278083.16  Difference:   -2.1%
>  PartitionedNonIndexedQueryBenchmark avg ops/sec  
> Baseline:99.45  Test:   101.97  Difference:   +2.5%
>  avg latency  
> Baseline: 723415530.75  Test: 705653061.86  Difference:   -2.5%
>   PartitionedPutAllBenchmark avg ops/sec  
> Baseline:  7921.61  Test:  7816.66  Difference:   -1.3%
>  avg latency  
> Baseline:  18172638.37  Test:  18416169.28  Difference:   +1.3%
>   PartitionedPutAllLongBenchmark avg ops/sec  
> Baseline:  1379.53  Test:  1169.16  Difference:  -15.2%
>  avg latency  
> Baseline: 105140260.44  Test: 123722914.94  Difference:  +17.7%
>  PartitionedPutBenchmark avg ops/sec  
> Baseline:474986.11  Test: 

[jira] [Commented] (GEODE-9038) CI Failure: ShutdownAllDUnitTest > testShutdownAllWithMembersWaiting fails with suspect strings

2021-08-21 Thread Geode Integration (Jira)


[ 
https://issues.apache.org/jira/browse/GEODE-9038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17402727#comment-17402727
 ] 

Geode Integration commented on GEODE-9038:
--

Seen in [distributed-test-openjdk8 
#1385|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/1385]
 ... see [test 
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0426/test-results/distributedTest/1629581792/]
 or download 
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0426/test-artifacts/1629581792/distributedtestfiles-openjdk8-1.15.0-build.0426.tgz].

> CI Failure: ShutdownAllDUnitTest > testShutdownAllWithMembersWaiting fails 
> with suspect strings
> ---
>
> Key: GEODE-9038
> URL: https://issues.apache.org/jira/browse/GEODE-9038
> Project: Geode
>  Issue Type: Bug
>Reporter: John Hutchison
>Priority: Major
>
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/78
> org.apache.geode.internal.cache.partitioned.ShutdownAllDUnitTest > 
> testShutdownAllWithMembersWaiting FAILED
> 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 'dunit_suspect-vm0.log' at line 1246
> [fatal 2021/03/15 19:27:44.311 GMT  
> tid=1461] While pushing message  unexpected exception during data cleanup" level WARNING> to recipients: 
> <172.17.0.7(179):41003>
> org.apache.geode.alerting.internal.spi.AlertingIOException: 
> java.io.IOException: Cannot form connection to alert listener 
> 172.17.0.7(179):41003
>   at 
> org.apache.geode.internal.tcp.TCPConduit.getConnection(TCPConduit.java:884)
>   at 
> org.apache.geode.distributed.internal.direct.DirectChannel.getConnections(DirectChannel.java:464)
>   at 
> org.apache.geode.distributed.internal.direct.DirectChannel.sendToMany(DirectChannel.java:280)
>   at 
> org.apache.geode.distributed.internal.direct.DirectChannel.sendToOne(DirectChannel.java:187)
>   at 
> org.apache.geode.distributed.internal.direct.DirectChannel.send(DirectChannel.java:523)
>   at 
> org.apache.geode.distributed.internal.DistributionImpl.directChannelSend(DistributionImpl.java:346)
>   at 
> org.apache.geode.distributed.internal.DistributionImpl.send(DistributionImpl.java:291)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.sendViaMembershipManager(ClusterDistributionManager.java:2053)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.sendOutgoing(ClusterDistributionManager.java:1981)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.sendMessage(ClusterDistributionManager.java:2018)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.putOutgoing(ClusterDistributionManager.java:1083)
>   at 
> org.apache.geode.alerting.internal.ClusterAlertMessaging.lambda$null$0(ClusterAlertMessaging.java:103)
>   at 
> org.apache.geode.alerting.internal.spi.AlertingAction.execute(AlertingAction.java:34)
>   at 
> org.apache.geode.alerting.internal.ClusterAlertMessaging.lambda$sendAlert$1(ClusterAlertMessaging.java:81)
>   at 
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
>   at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
>   at 
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
>   at 
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
>   at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: java.io.IOException: Cannot form connection to alert listener 
> 172.17.0.7(179):41003
>   at 
> org.apache.geode.internal.tcp.ConnectionTable.getSharedConnection(ConnectionTable.java:406)
>   at 
> org.apache.geode.internal.tcp.ConnectionTable.get(ConnectionTable.java:574)
>   at 
> org.apache.geode.internal.tcp.TCPConduit.getConnection(TCPConduit.java:803)
>   ... 18 more



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (GEODE-8644) SerialGatewaySenderQueueDUnitTest.unprocessedTokensMapShouldDrainCompletely() intermittently fails when queues drain too slowly

2021-08-21 Thread Geode Integration (Jira)


[ 
https://issues.apache.org/jira/browse/GEODE-8644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17402725#comment-17402725
 ] 

Geode Integration commented on GEODE-8644:
--

Seen in [distributed-test-openjdk8 
#1378|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/1378]
 ... see [test 
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0426/test-results/distributedTest/1629575179/]
 or download 
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0426/test-artifacts/1629575179/distributedtestfiles-openjdk8-1.15.0-build.0426.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: Benjamin P Ross
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.14.0
>
>
> 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.3.4#803005)


[jira] [Commented] (GEODE-6714) CI failure: org.apache.geode.management.internal.rest.ClusterManagementLocatorReconnectDunitTest.clusterManagementRestServiceStillWorksAfterLocatorReconnects

2021-08-21 Thread Geode Integration (Jira)


[ 
https://issues.apache.org/jira/browse/GEODE-6714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17402723#comment-17402723
 ] 

Geode Integration commented on GEODE-6714:
--

Seen in [distributed-test-openjdk8 
#1352|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/1352]
 ... see [test 
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0426/test-results/distributedTest/1629556095/]
 or download 
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0426/test-artifacts/1629556095/distributedtestfiles-openjdk8-1.15.0-build.0426.tgz].

> CI failure: 
> org.apache.geode.management.internal.rest.ClusterManagementLocatorReconnectDunitTest.clusterManagementRestServiceStillWorksAfterLocatorReconnects
> -
>
> Key: GEODE-6714
> URL: https://issues.apache.org/jira/browse/GEODE-6714
> Project: Geode
>  Issue Type: Bug
>  Components: ci
>Affects Versions: 1.9.0
>Reporter: Dick Cavender
>Priority: Major
>
> {noformat}
> org.apache.geode.management.internal.rest.ClusterManagementLocatorReconnectDunitTest
>  > clusterManagementRestServiceStillWorksAfterLocatorReconnects FAILED
> org.awaitility.core.ConditionTimeoutException: Condition with lambda 
> expression in 
> org.apache.geode.management.internal.rest.ClusterManagementLocatorReconnectDunitTest
>  was not fulfilled within 300 seconds.
> at 
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:145)
> at 
> org.awaitility.core.CallableCondition.await(CallableCondition.java:79)
> at 
> org.awaitility.core.CallableCondition.await(CallableCondition.java:27)
> at 
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:902)
> at 
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:860)
> at 
> org.apache.geode.management.internal.rest.ClusterManagementLocatorReconnectDunitTest.clusterManagementRestServiceStillWorksAfterLocatorReconnects(ClusterManagementLocatorReconnectDunitTest.java:63)
> 213 tests completed, 1 failed
>  {noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (GEODE-9038) CI Failure: ShutdownAllDUnitTest > testShutdownAllWithMembersWaiting fails with suspect strings

2021-08-21 Thread Geode Integration (Jira)


[ 
https://issues.apache.org/jira/browse/GEODE-9038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17402722#comment-17402722
 ] 

Geode Integration commented on GEODE-9038:
--

Seen in [distributed-test-openjdk8 
#1341|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/1341]
 ... see [test 
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0426/test-results/distributedTest/1629548516/]
 or download 
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0426/test-artifacts/1629548516/distributedtestfiles-openjdk8-1.15.0-build.0426.tgz].

> CI Failure: ShutdownAllDUnitTest > testShutdownAllWithMembersWaiting fails 
> with suspect strings
> ---
>
> Key: GEODE-9038
> URL: https://issues.apache.org/jira/browse/GEODE-9038
> Project: Geode
>  Issue Type: Bug
>Reporter: John Hutchison
>Priority: Major
>
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/78
> org.apache.geode.internal.cache.partitioned.ShutdownAllDUnitTest > 
> testShutdownAllWithMembersWaiting FAILED
> 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 'dunit_suspect-vm0.log' at line 1246
> [fatal 2021/03/15 19:27:44.311 GMT  
> tid=1461] While pushing message  unexpected exception during data cleanup" level WARNING> to recipients: 
> <172.17.0.7(179):41003>
> org.apache.geode.alerting.internal.spi.AlertingIOException: 
> java.io.IOException: Cannot form connection to alert listener 
> 172.17.0.7(179):41003
>   at 
> org.apache.geode.internal.tcp.TCPConduit.getConnection(TCPConduit.java:884)
>   at 
> org.apache.geode.distributed.internal.direct.DirectChannel.getConnections(DirectChannel.java:464)
>   at 
> org.apache.geode.distributed.internal.direct.DirectChannel.sendToMany(DirectChannel.java:280)
>   at 
> org.apache.geode.distributed.internal.direct.DirectChannel.sendToOne(DirectChannel.java:187)
>   at 
> org.apache.geode.distributed.internal.direct.DirectChannel.send(DirectChannel.java:523)
>   at 
> org.apache.geode.distributed.internal.DistributionImpl.directChannelSend(DistributionImpl.java:346)
>   at 
> org.apache.geode.distributed.internal.DistributionImpl.send(DistributionImpl.java:291)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.sendViaMembershipManager(ClusterDistributionManager.java:2053)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.sendOutgoing(ClusterDistributionManager.java:1981)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.sendMessage(ClusterDistributionManager.java:2018)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.putOutgoing(ClusterDistributionManager.java:1083)
>   at 
> org.apache.geode.alerting.internal.ClusterAlertMessaging.lambda$null$0(ClusterAlertMessaging.java:103)
>   at 
> org.apache.geode.alerting.internal.spi.AlertingAction.execute(AlertingAction.java:34)
>   at 
> org.apache.geode.alerting.internal.ClusterAlertMessaging.lambda$sendAlert$1(ClusterAlertMessaging.java:81)
>   at 
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
>   at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
>   at 
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
>   at 
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
>   at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: java.io.IOException: Cannot form connection to alert listener 
> 172.17.0.7(179):41003
>   at 
> org.apache.geode.internal.tcp.ConnectionTable.getSharedConnection(ConnectionTable.java:406)
>   at 
> org.apache.geode.internal.tcp.ConnectionTable.get(ConnectionTable.java:574)
>   at 
> org.apache.geode.internal.tcp.TCPConduit.getConnection(TCPConduit.java:803)
>   ... 18 more



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (GEODE-8644) SerialGatewaySenderQueueDUnitTest.unprocessedTokensMapShouldDrainCompletely() intermittently fails when queues drain too slowly

2021-08-21 Thread Geode Integration (Jira)


[ 
https://issues.apache.org/jira/browse/GEODE-8644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17402721#comment-17402721
 ] 

Geode Integration commented on GEODE-8644:
--

Seen in [distributed-test-openjdk8 
#1343|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/1343]
 ... see [test 
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0426/test-results/distributedTest/1629548494/]
 or download 
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0426/test-artifacts/1629548494/distributedtestfiles-openjdk8-1.15.0-build.0426.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: Benjamin P Ross
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.14.0
>
>
> 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.3.4#803005)


[jira] [Commented] (GEODE-7710) CI Failure: JMXMBeanReconnectDUnitTest aka JmxServerReconnectDistributedTest fails intermittently because one locator is missing the LockServiceMXBean

2021-08-21 Thread Geode Integration (Jira)


[ 
https://issues.apache.org/jira/browse/GEODE-7710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17402720#comment-17402720
 ] 

Geode Integration commented on GEODE-7710:
--

Seen in [distributed-test-openjdk8 
#1317|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/1317]
 ... see [test 
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0426/test-results/distributedTest/1629525000/]
 or download 
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0426/test-artifacts/1629525000/distributedtestfiles-openjdk8-1.15.0-build.0426.tgz].

> CI Failure: JMXMBeanReconnectDUnitTest aka JmxServerReconnectDistributedTest 
> fails intermittently because one locator is missing the LockServiceMXBean
> --
>
> Key: GEODE-7710
> URL: https://issues.apache.org/jira/browse/GEODE-7710
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Affects Versions: 1.13.0
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
>  Labels: GeodeOperationAPI, flaky, pull-request-available
>  Time Spent: 5h
>  Remaining Estimate: 0h
>
> Multiple tests in JMXMBeanReconnectDUnitTest may fail an await due to one of 
> the locators missing the LockServiceMXBean for the cluster config service.
> {noformat}
> but could not find:
>  
> <[GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator1]>
> {noformat}
> These test failures are caused by *GEODE-7739*.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (GEODE-9038) CI Failure: ShutdownAllDUnitTest > testShutdownAllWithMembersWaiting fails with suspect strings

2021-08-21 Thread Geode Integration (Jira)


[ 
https://issues.apache.org/jira/browse/GEODE-9038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17402719#comment-17402719
 ] 

Geode Integration commented on GEODE-9038:
--

Seen in [distributed-test-openjdk8 
#1306|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/1306]
 ... see [test 
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0426/test-results/distributedTest/1629517523/]
 or download 
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0426/test-artifacts/1629517523/distributedtestfiles-openjdk8-1.15.0-build.0426.tgz].

> CI Failure: ShutdownAllDUnitTest > testShutdownAllWithMembersWaiting fails 
> with suspect strings
> ---
>
> Key: GEODE-9038
> URL: https://issues.apache.org/jira/browse/GEODE-9038
> Project: Geode
>  Issue Type: Bug
>Reporter: John Hutchison
>Priority: Major
>
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/78
> org.apache.geode.internal.cache.partitioned.ShutdownAllDUnitTest > 
> testShutdownAllWithMembersWaiting FAILED
> 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 'dunit_suspect-vm0.log' at line 1246
> [fatal 2021/03/15 19:27:44.311 GMT  
> tid=1461] While pushing message  unexpected exception during data cleanup" level WARNING> to recipients: 
> <172.17.0.7(179):41003>
> org.apache.geode.alerting.internal.spi.AlertingIOException: 
> java.io.IOException: Cannot form connection to alert listener 
> 172.17.0.7(179):41003
>   at 
> org.apache.geode.internal.tcp.TCPConduit.getConnection(TCPConduit.java:884)
>   at 
> org.apache.geode.distributed.internal.direct.DirectChannel.getConnections(DirectChannel.java:464)
>   at 
> org.apache.geode.distributed.internal.direct.DirectChannel.sendToMany(DirectChannel.java:280)
>   at 
> org.apache.geode.distributed.internal.direct.DirectChannel.sendToOne(DirectChannel.java:187)
>   at 
> org.apache.geode.distributed.internal.direct.DirectChannel.send(DirectChannel.java:523)
>   at 
> org.apache.geode.distributed.internal.DistributionImpl.directChannelSend(DistributionImpl.java:346)
>   at 
> org.apache.geode.distributed.internal.DistributionImpl.send(DistributionImpl.java:291)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.sendViaMembershipManager(ClusterDistributionManager.java:2053)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.sendOutgoing(ClusterDistributionManager.java:1981)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.sendMessage(ClusterDistributionManager.java:2018)
>   at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.putOutgoing(ClusterDistributionManager.java:1083)
>   at 
> org.apache.geode.alerting.internal.ClusterAlertMessaging.lambda$null$0(ClusterAlertMessaging.java:103)
>   at 
> org.apache.geode.alerting.internal.spi.AlertingAction.execute(AlertingAction.java:34)
>   at 
> org.apache.geode.alerting.internal.ClusterAlertMessaging.lambda$sendAlert$1(ClusterAlertMessaging.java:81)
>   at 
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
>   at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
>   at 
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
>   at 
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
>   at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: java.io.IOException: Cannot form connection to alert listener 
> 172.17.0.7(179):41003
>   at 
> org.apache.geode.internal.tcp.ConnectionTable.getSharedConnection(ConnectionTable.java:406)
>   at 
> org.apache.geode.internal.tcp.ConnectionTable.get(ConnectionTable.java:574)
>   at 
> org.apache.geode.internal.tcp.TCPConduit.getConnection(TCPConduit.java:803)
>   ... 18 more



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (GEODE-9528) CI Failure: DistributionAdvisorIntegrationTest > verifyMembershipListenerIsRemovedAfterForceDisconnect

2021-08-21 Thread Geode Integration (Jira)


[ 
https://issues.apache.org/jira/browse/GEODE-9528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17402717#comment-17402717
 ] 

Geode Integration commented on GEODE-9528:
--

Seen in [integration-test-openjdk8 
#135|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/integration-test-openjdk8/builds/135]
 ... see [test 
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0426/test-results/integrationTest/1629506741/]
 or download 
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0426/test-artifacts/1629506741/integrationtestfiles-openjdk8-1.15.0-build.0426.tgz].

> CI Failure: DistributionAdvisorIntegrationTest > 
> verifyMembershipListenerIsRemovedAfterForceDisconnect
> --
>
> Key: GEODE-9528
> URL: https://issues.apache.org/jira/browse/GEODE-9528
> Project: Geode
>  Issue Type: Bug
>  Components: membership
>Affects Versions: 1.12.5, 1.13.5, 1.14.0
>Reporter: Owen Nichols
>Priority: Major
>  Labels: blocks-1.12.5, blocks-1.13.5, blocks-1.14.0​
>
> {noformat}
> org.apache.geode.distributed.internal.DistributionAdvisorIntegrationTest > 
> verifyMembershipListenerIsRemovedAfterForceDisconnect FAILED
> org.junit.ComparisonFailure: expected:<[fals]e> but was:<[tru]e>
> at 
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at 
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at 
> jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at 
> org.apache.geode.distributed.internal.DistributionAdvisorIntegrationTest.verifyMembershipListenerIsRemovedAfterForceDisconnect(DistributionAdvisorIntegrationTest.java:57)
>  {noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (GEODE-9528) CI Failure: DistributionAdvisorIntegrationTest > verifyMembershipListenerIsRemovedAfterForceDisconnect

2021-08-21 Thread Geode Integration (Jira)


[ 
https://issues.apache.org/jira/browse/GEODE-9528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17402718#comment-17402718
 ] 

Geode Integration commented on GEODE-9528:
--

Seen in [integration-test-openjdk11 
#134|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/integration-test-openjdk11/builds/134]
 ... see [test 
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0426/test-results/integrationTest/1629506688/]
 or download 
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0426/test-artifacts/1629506688/integrationtestfiles-openjdk11-1.15.0-build.0426.tgz].

> CI Failure: DistributionAdvisorIntegrationTest > 
> verifyMembershipListenerIsRemovedAfterForceDisconnect
> --
>
> Key: GEODE-9528
> URL: https://issues.apache.org/jira/browse/GEODE-9528
> Project: Geode
>  Issue Type: Bug
>  Components: membership
>Affects Versions: 1.12.5, 1.13.5, 1.14.0
>Reporter: Owen Nichols
>Priority: Major
>  Labels: blocks-1.12.5, blocks-1.13.5, blocks-1.14.0​
>
> {noformat}
> org.apache.geode.distributed.internal.DistributionAdvisorIntegrationTest > 
> verifyMembershipListenerIsRemovedAfterForceDisconnect FAILED
> org.junit.ComparisonFailure: expected:<[fals]e> but was:<[tru]e>
> at 
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at 
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at 
> jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at 
> org.apache.geode.distributed.internal.DistributionAdvisorIntegrationTest.verifyMembershipListenerIsRemovedAfterForceDisconnect(DistributionAdvisorIntegrationTest.java:57)
>  {noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (GEODE-8644) SerialGatewaySenderQueueDUnitTest.unprocessedTokensMapShouldDrainCompletely() intermittently fails when queues drain too slowly

2021-08-21 Thread Geode Integration (Jira)


[ 
https://issues.apache.org/jira/browse/GEODE-8644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17402716#comment-17402716
 ] 

Geode Integration commented on GEODE-8644:
--

Seen in [distributed-test-openjdk11 
#137|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/distributed-test-openjdk11/builds/137]
 ... see [test 
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0426/test-results/distributedTest/1629512983/]
 or download 
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0426/test-artifacts/1629512983/distributedtestfiles-openjdk11-1.15.0-build.0426.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: Benjamin P Ross
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.14.0
>
>
> 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.3.4#803005)