[jira] [Created] (GEODE-9521) Add test to cover multi-servers scenario for re-authentication
Jinmei Liao created GEODE-9521: -- Summary: Add test to cover multi-servers scenario for re-authentication Key: GEODE-9521 URL: https://issues.apache.org/jira/browse/GEODE-9521 Project: Geode Issue Type: Sub-task Reporter: Jinmei Liao -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9453) The server, once a user expires, should clean the user attributes from the server.
[ https://issues.apache.org/jira/browse/GEODE-9453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao updated GEODE-9453: --- Description: ClientUserAuths maintains a map of clientID to its user attributes (the logged in shiro subject etc), when user expires, we need to remove that entry from that map and log the shiro subject out to avoid resource leak. make sure to include tests in multi-server cases was:ClientUserAuths maintains a map of clientID to its user attributes (the logged in shiro subject etc), when user expires, we need to remove that entry from that map and log the shiro subject out to avoid resource leak. > The server, once a user expires, should clean the user attributes from the > server. > -- > > Key: GEODE-9453 > URL: https://issues.apache.org/jira/browse/GEODE-9453 > Project: Geode > Issue Type: Sub-task > Components: core, security >Reporter: Jinmei Liao >Priority: Major > Labels: GeodeOperationAPI > > ClientUserAuths maintains a map of clientID to its user attributes (the > logged in shiro subject etc), when user expires, we need to remove that entry > from that map and log the shiro subject out to avoid resource leak. > > make sure to include tests in multi-server cases -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9453) The server, once a user expires, should clean the user attributes from the server.
[ https://issues.apache.org/jira/browse/GEODE-9453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao updated GEODE-9453: --- Description: ClientUserAuths maintains a map of clientID to its user attributes (the logged in shiro subject etc), when user expires, we need to remove that entry from that map and log the shiro subject out to avoid resource leak. make sure to include tests in multi-server cases was: ClientUserAuths maintains a map of clientID to its user attributes (the logged in shiro subject etc), when user expires, we need to remove that entry from that map and log the shiro subject out to avoid resource leak. make sure to include tests in multi-server cases > The server, once a user expires, should clean the user attributes from the > server. > -- > > Key: GEODE-9453 > URL: https://issues.apache.org/jira/browse/GEODE-9453 > Project: Geode > Issue Type: Sub-task > Components: core, security >Reporter: Jinmei Liao >Priority: Major > Labels: GeodeOperationAPI > > ClientUserAuths maintains a map of clientID to its user attributes (the > logged in shiro subject etc), when user expires, we need to remove that entry > from that map and log the shiro subject out to avoid resource leak. > make sure to include tests in multi-server cases -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9458) Add tests for functions executions on servers when authentication expires
[ https://issues.apache.org/jira/browse/GEODE-9458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao updated GEODE-9458: --- Description: and make sure the behavior matches expectation. make sure to include tests in multi-server cases was:and make sure the behavior matches expection. > Add tests for functions executions on servers when authentication expires > - > > Key: GEODE-9458 > URL: https://issues.apache.org/jira/browse/GEODE-9458 > Project: Geode > Issue Type: Sub-task >Reporter: Jinmei Liao >Priority: Major > Labels: GeodeOperationAPI > > and make sure the behavior matches expectation. > > make sure to include tests in multi-server cases -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9457) Investigate the behavior of CQ and registered interests when authentication expires.
[ https://issues.apache.org/jira/browse/GEODE-9457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao updated GEODE-9457: --- Description: We need to find out what's the current behavior of cq and registered interests when authentication expires and see if the behavior matches the expectation make sure to include tests in multi-server cases was:We need to find out what's the current behavior of cq and registered interests when authentication expires and see if the behavior matches the expectation > Investigate the behavior of CQ and registered interests when authentication > expires. > > > Key: GEODE-9457 > URL: https://issues.apache.org/jira/browse/GEODE-9457 > Project: Geode > Issue Type: Sub-task > Components: core, security >Reporter: Jinmei Liao >Priority: Major > Labels: GeodeOperationAPI > > We need to find out what's the current behavior of cq and registered > interests when authentication expires and see if the behavior matches the > expectation > make sure to include tests in multi-server cases -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9460) add tests for multi-user mode when one user expires
[ https://issues.apache.org/jira/browse/GEODE-9460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao updated GEODE-9460: --- Description: make sure the behavior matches expectations make sure to include tests in multi-server cases was:make sure the behavior matches expections > add tests for multi-user mode when one user expires > --- > > Key: GEODE-9460 > URL: https://issues.apache.org/jira/browse/GEODE-9460 > Project: Geode > Issue Type: Sub-task >Reporter: Jinmei Liao >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > > make sure the behavior matches expectations > > make sure to include tests in multi-server cases -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9521) Add test to cover multi-servers scenario for re-authentication
[ https://issues.apache.org/jira/browse/GEODE-9521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao updated GEODE-9521: --- Labels: GeodeOperationAPI security (was: ) > Add test to cover multi-servers scenario for re-authentication > -- > > Key: GEODE-9521 > URL: https://issues.apache.org/jira/browse/GEODE-9521 > Project: Geode > Issue Type: Sub-task >Reporter: Jinmei Liao >Priority: Major > Labels: GeodeOperationAPI, security > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9184) Implement ZLEXCOUNT Command
[ https://issues.apache.org/jira/browse/GEODE-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401741#comment-17401741 ] ASF subversion and git services commented on GEODE-9184: Commit 7835dc65c4901af38955ca466d098e3ebaed2463 in geode's branch refs/heads/develop from Jens Deppe [ https://gitbox.apache.org/repos/asf?p=geode.git;h=7835dc6 ] GEODE-9184: Add Radish ZLEXCOUNT command (#6735) > Implement ZLEXCOUNT Command > --- > > Key: GEODE-9184 > URL: https://issues.apache.org/jira/browse/GEODE-9184 > Project: Geode > Issue Type: New Feature > Components: redis >Reporter: Wayne >Priority: Major > Labels: blocks-1.15.0, pull-request-available, redis > > Implement the [ZLEXCOUNT|https://redis.io/commands/zlexcount] command. > > +Acceptance Criteria+ > The ZLEXCOUNT command has been implemented and unit tests are added to ensure > the command works as expected. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9184) Implement ZLEXCOUNT Command
[ https://issues.apache.org/jira/browse/GEODE-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jens Deppe resolved GEODE-9184. --- Fix Version/s: 1.15.0 Resolution: Fixed > Implement ZLEXCOUNT Command > --- > > Key: GEODE-9184 > URL: https://issues.apache.org/jira/browse/GEODE-9184 > Project: Geode > Issue Type: New Feature > Components: redis >Reporter: Wayne >Priority: Major > Labels: blocks-1.15.0, pull-request-available, redis > Fix For: 1.15.0 > > > Implement the [ZLEXCOUNT|https://redis.io/commands/zlexcount] command. > > +Acceptance Criteria+ > The ZLEXCOUNT command has been implemented and unit tests are added to ensure > the command works as expected. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9186) Implement ZPOPMIN Command
[ https://issues.apache.org/jira/browse/GEODE-9186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jens Deppe resolved GEODE-9186. --- Fix Version/s: 1.15.0 Resolution: Fixed > Implement ZPOPMIN Command > - > > Key: GEODE-9186 > URL: https://issues.apache.org/jira/browse/GEODE-9186 > Project: Geode > Issue Type: New Feature > Components: redis >Reporter: Wayne >Priority: Major > Labels: blocks-1.15.0, pull-request-available, redis > Fix For: 1.15.0 > > > Implement the [ZPOPMIN|https://redis.io/commands/zpopmin] command. > > +Acceptance Criteria+ > The ZPOPMIN command has been implemented and unit tests have been added to > assert that the command works as expected. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9522) Operations to replicate region were notified registered client in misorder due to switching primary queue
Xiaojian Zhou created GEODE-9522: Summary: Operations to replicate region were notified registered client in misorder due to switching primary queue Key: GEODE-9522 URL: https://issues.apache.org/jira/browse/GEODE-9522 Project: Geode Issue Type: Bug Reporter: Xiaojian Zhou When a client is doing puts (mainly creates) to servers with replicated region, shutdown some servers to force switching of primary HARegionQueue, sometimes, the event with later event id is distributed by previous primary HARegionQueue, which caused the events with earlier event ids are rejected by clients. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9523) ContainerInstall Resource path invalid on Windows
Dale Emery created GEODE-9523:
-
Summary: ContainerInstall Resource path invalid on Windows
Key: GEODE-9523
URL: https://issues.apache.org/jira/browse/GEODE-9523
Project: Geode
Issue Type: Test
Components: tests
Reporter: Dale Emery
The {{ContainerInstall}} test helper creates an installer using this code:
{noformat}
String resource = getResource(getClass(), "/" + downloadURL).getPath();
URL url = Paths.get(resource).toUri().toURL();
Installer installer = new ZipURLInstaller(url, TMP_DIR + "/downloads",
installDir);
{noformat}
On Windows, the {{resource}} string is not a valid {{Path}}, and the second
line throws an exception:
_java.nio.file.InvalidPathException: Illegal char <:> at index 2:
/C:/Users/geode/geode/geode-assembly/build/resources/distributedTest/tomcat-9.0.48.zip_
The chain of conversions is unnecessary. On Windows, the URL returned from
{{getResource(...)}} is a perfectly fine URL to pass to the {{ZipURLInstaller}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9302) Benchmark instability in PartitionedPutStringBenchmark
[
https://issues.apache.org/jira/browse/GEODE-9302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401750#comment-17401750
]
Geode Integration commented on GEODE-9302:
--
Seen in [benchmark-base
#128|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/benchmark-base/builds/128].
> Benchmark instability in PartitionedPutStringBenchmark
> --
>
> Key: GEODE-9302
> URL: https://issues.apache.org/jira/browse/GEODE-9302
> Project: Geode
> Issue Type: Bug
> Components: benchmarks
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Priority: Major
>
> A benchmark failure due to the recently-introduced
> PartitionedPutStringBenchmark was observed:
> {noformat}
> This is ITERATION 1 of benchmarking against baseline.
> P2pPartitionedGetBenchmark avg ops/sec
> Baseline:853001.60 Test:867151.67 Difference: +1.7%
> avg latency
> Baseline:842007.55 Test:828545.06 Difference: -1.6%
> P2pPartitionedPutBenchmark avg ops/sec
> Baseline:128283.47 Test:126510.92 Difference: -1.4%
> avg latency
> Baseline: 5785619.62 Test: 5915913.49 Difference: +2.3%
> P2pPartitionedPutBytesBenchmark avg ops/sec
> Baseline:175658.08 Test:174865.97 Difference: -0.5%
> avg latency
> Baseline: 4130071.43 Test: 4130753.09 Difference: +0.0%
>PartitionedFunctionExecutionBenchmark avg ops/sec
> Baseline:254788.26 Test:268132.99 Difference: +5.2%
> avg latency
> Baseline:846158.41 Test:804199.42 Difference: -5.0%
> PartitionedFunctionExecutionWithArgumentsBenchmark avg ops/sec
> Baseline:278669.87 Test:281504.58 Difference: +1.0%
> avg latency
> Baseline: 1031826.82 Test: 1021314.54 Difference: -1.0%
> PartitionedFunctionExecutionWithFiltersBenchmark avg ops/sec
> Baseline:372204.82 Test:348815.81 Difference: -6.3%
> avg latency
> Baseline: 1545217.38 Test: 1649706.37 Difference: +6.8%
> PartitionedGetBenchmark avg ops/sec
> Baseline:823740.09 Test:819044.99 Difference: -0.6%
> avg latency
> Baseline:872172.75 Test:877580.02 Difference: +0.6%
> PartitionedGetLongBenchmark avg ops/sec
> Baseline: 1047221.43 Test: 1045565.89 Difference: -0.2%
> avg latency
> Baseline:685757.55 Test:687005.43 Difference: +0.2%
>PartitionedGetStringBenchmark avg ops/sec
> Baseline: 1055904.14 Test: 1045420.73 Difference: -1.0%
> avg latency
> Baseline:680031.44 Test:687045.15 Difference: +1.0%
> PartitionedIndexedQueryBenchmark avg ops/sec
> Baseline: 31596.35 Test: 31653.48 Difference: +0.2%
> avg latency
> Baseline: 18221302.10 Test: 18216097.86 Difference: -0.0%
> PartitionedNonIndexedQueryBenchmark avg ops/sec
> Baseline:95.78 Test: 100.35 Difference: +4.8%
> avg latency
> Baseline: 750871203.78 Test: 716853923.95 Difference: -4.5%
> PartitionedPutAllBenchmark avg ops/sec
> Baseline: 8675.75 Test: 8628.10 Difference: -0.5%
> avg latency
> Baseline: 16595044.73 Test: 16685258.91 Difference: +0.5%
> PartitionedPutAllLongBenchmark avg ops/sec
> Baseline: 1382.38 Test: 1380.50 Difference: -0.1%
> avg latency
> Baseline: 104866853.92 Test: 104775538.34 Difference: -0.1%
> PartitionedPutBenchmark avg ops/sec
> Baseline:491790.40 Test:479926.75 Difference: -2.4%
> avg latency
> Baseline: 1461947.23 Test: 1497519.77 Difference: +2.4%
>
[jira] [Commented] (GEODE-9169) Remove Context Switch Between Netty and Command Queue Thread
[ https://issues.apache.org/jira/browse/GEODE-9169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401768#comment-17401768 ] ASF subversion and git services commented on GEODE-9169: Commit ed38145379d3da05ecc79a39fa145030bbd4fb1e in geode's branch refs/heads/expireAuthentication from Hale Bales [ https://gitbox.apache.org/repos/asf?p=geode.git;h=ed38145 ] GEODE-9169: remove netty context switch (#6725) GEODE-9169: Remove Netty context switch Instead of submitting commands to a background executor, this removes that context switch and performs the command right on the netty thread. Removing the context switch provides a significant performance improvement. Signed-off-by: Donal Evans > Remove Context Switch Between Netty and Command Queue Thread > > > Key: GEODE-9169 > URL: https://issues.apache.org/jira/browse/GEODE-9169 > Project: Geode > Issue Type: New Feature > Components: redis >Reporter: Wayne >Assignee: Hale Bales >Priority: Major > Labels: blocks-1.15.0, performance, pull-request-available, > redis > Fix For: 1.15.0 > > > On the current develop branch, the Netty thread reads a message and then puts > it on a queue for another thread to process. Performing the region update > directly on the Netty thread significantly improved performance. > The original behavior was there to support pub/sub use cases, where we need > to push updates to the Netty channel, as well as following Netty best > practices of not blocking the Netty thread. We need to see how we can make > this same change on develop to avoid the context switch while still > supporting pub/sub and not breaking other use cases. > +Acceptance Criteria+ > The context switch between the Netty and command queue thread has been > removed for all commands that are not pub/sub related. > Geode benchmarks perform better after this change for all non-pubsub commands. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9186) Implement ZPOPMIN Command
[ https://issues.apache.org/jira/browse/GEODE-9186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401770#comment-17401770 ] ASF subversion and git services commented on GEODE-9186: Commit befc7cc44b10fa133e50e757eab5ec8b1b10bb8f in geode's branch refs/heads/expireAuthentication from Jens Deppe [ https://gitbox.apache.org/repos/asf?p=geode.git;h=befc7cc ] GEODE-9186: Add Radish ZPOPMIN command (#6738) > Implement ZPOPMIN Command > - > > Key: GEODE-9186 > URL: https://issues.apache.org/jira/browse/GEODE-9186 > Project: Geode > Issue Type: New Feature > Components: redis >Reporter: Wayne >Priority: Major > Labels: blocks-1.15.0, pull-request-available, redis > Fix For: 1.15.0 > > > Implement the [ZPOPMIN|https://redis.io/commands/zpopmin] command. > > +Acceptance Criteria+ > The ZPOPMIN command has been implemented and unit tests have been added to > assert that the command works as expected. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9169) Remove Context Switch Between Netty and Command Queue Thread
[ https://issues.apache.org/jira/browse/GEODE-9169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401769#comment-17401769 ] ASF subversion and git services commented on GEODE-9169: Commit ed38145379d3da05ecc79a39fa145030bbd4fb1e in geode's branch refs/heads/expireAuthentication from Hale Bales [ https://gitbox.apache.org/repos/asf?p=geode.git;h=ed38145 ] GEODE-9169: remove netty context switch (#6725) GEODE-9169: Remove Netty context switch Instead of submitting commands to a background executor, this removes that context switch and performs the command right on the netty thread. Removing the context switch provides a significant performance improvement. Signed-off-by: Donal Evans > Remove Context Switch Between Netty and Command Queue Thread > > > Key: GEODE-9169 > URL: https://issues.apache.org/jira/browse/GEODE-9169 > Project: Geode > Issue Type: New Feature > Components: redis >Reporter: Wayne >Assignee: Hale Bales >Priority: Major > Labels: blocks-1.15.0, performance, pull-request-available, > redis > Fix For: 1.15.0 > > > On the current develop branch, the Netty thread reads a message and then puts > it on a queue for another thread to process. Performing the region update > directly on the Netty thread significantly improved performance. > The original behavior was there to support pub/sub use cases, where we need > to push updates to the Netty channel, as well as following Netty best > practices of not blocking the Netty thread. We need to see how we can make > this same change on develop to avoid the context switch while still > supporting pub/sub and not breaking other use cases. > +Acceptance Criteria+ > The context switch between the Netty and command queue thread has been > removed for all commands that are not pub/sub related. > Geode benchmarks perform better after this change for all non-pubsub commands. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9490) CI failure: NativeRedisSessionAcceptanceTest > executionError
[
https://issues.apache.org/jira/browse/GEODE-9490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401767#comment-17401767
]
ASF subversion and git services commented on GEODE-9490:
Commit a1df4b3be86c6ac8668770a88210c3cb5f15abef in geode's branch
refs/heads/expireAuthentication from Jens Deppe
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=a1df4b3 ]
GEODE-9490: Correctly ignore RedisProxy exceptions in
NativeRedisClusterTestRule (#6745)
> CI failure: NativeRedisSessionAcceptanceTest > executionError
> -
>
> Key: GEODE-9490
> URL: https://issues.apache.org/jira/browse/GEODE-9490
> Project: Geode
> Issue Type: Test
> Components: redis, tests
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> {noformat}
> NativeRedisSessionAcceptanceTest > executionError 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-local.log' at line 1611
> [error 2021/08/05 23:35:01.484 UTC tid=78] Failed to
> return response on inboundChannel
> io.netty.channel.StacklessClosedChannelException
> at io.netty.channel.AbstractChannel$AbstractUnsafe.write(Object,
> ChannelPromise)(Unknown Source)
> at org.junit.Assert.fail(Assert.java:89)
> at
> org.apache.geode.test.dunit.internal.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:409)
> at
> org.apache.geode.test.dunit.internal.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:425)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.after(ClusterStartupRule.java:186)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.access$100(ClusterStartupRule.java:70)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule$1.evaluate(ClusterStartupRule.java:141)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:115)
> at
> org.junit.vintage.engine.execution.RunnerExecutor.execute(RunnerExecutor.java:43)
> at
> java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183)
> at
> java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
> at java.util.Iterator.forEachRemaining(Iterator.java:116)
> at
> java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801)
> at
> java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:482)
> at
> java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472)
> at
> java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:150)
> at
> java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:173)
> at
> java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> at
> java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:485)
> at
> org.junit.vintage.engine.VintageTestEngine.executeAllChildren(VintageTestEngine.java:82)
> at
> org.junit.vintage.engine.VintageTestEngine.execute(VintageTestEngine.java:73)
> at
> org.junit.platform.launcher.core.EngineExecutionOrchestrator.execute(EngineExecutionOrchestrator.java:108)
> at
> org.junit.platform.launcher.core.EngineExecutionOrchestrator.execute(EngineExecutionOrchestrator.java:88)
> at
> org.junit.platform.launcher.core.EngineExecutionOrchestrator.lambda$execute$0(EngineExecutionOrchestrator.java:54)
> at
> org.junit.platform.launcher.core.EngineExecutionOrchestrator.withInterceptedStreams(EngineExecutionOrchestrator.java:67)
> at
> org.junit.platform.launcher.core.EngineExecutionOrchestrator.execute(EngineExecutionOrchestrator.java:52)
> at
> org.junit.platform.launcher.core.DefaultLauncher.execute(DefaultLauncher.java:96)
> at
> org.junit.platform.launcher.core.DefaultLauncher.execute(DefaultLauncher.java:75)
> at
> org.gradle.api.internal.tasks.testing.junitplatform.JUnitPlatformTestClassProcessor$CollectAllTestClassesExecutor.processAllTestClasses(JUnitPlatformTestClassProcessor.java:99)
> at
> org.gradle.api.internal.tasks.testing.junitplatform.JUnitPlatformTestClassProcessor$CollectAllTestClasses
[jira] [Commented] (GEODE-9074) CacheClientProxyStatistics messageQueueSize does not increase as events are added
[ https://issues.apache.org/jira/browse/GEODE-9074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401765#comment-17401765 ] ASF subversion and git services commented on GEODE-9074: Commit a10a56f573e9a4aabf3c5b6e3862539d6dd93b92 in geode's branch refs/heads/expireAuthentication from Mario Ivanac [ https://gitbox.apache.org/repos/asf?p=geode.git;h=a10a56f ] GEODE-9074: Added update of messageQueueSize at putting message to qu… (#6445) * GEODE-9074: Added update of messageQueueSize at putting message to queue. Also added new statistics messagesBeingQueuedInProgress and messagesBeingQueuedTime. > CacheClientProxyStatistics messageQueueSize does not increase as events are > added > - > > Key: GEODE-9074 > URL: https://issues.apache.org/jira/browse/GEODE-9074 > Project: Geode > Issue Type: Bug > Components: client queues >Reporter: Darrel Schneider >Assignee: Mario Ivanac >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > Fix For: 1.15.0 > > > Something I observed is that while a subscription queue was "full" the > default throttling caused geode to only add 10 events/sec to the queue. This > makes sense. But what didn't make sense was that the messageQueueSize did not > change by 10 events/sec even though, during this time, nothing was draining > from the queue. Then when the draining finally started (because the > CacheClientUpdater started running after a long register interest that had > been blocking it) we saw a huge spike in messageQueueSize when we should have > seen gradual growth. > In addition to improving messageQueueSize it would also be nice to have a > gauge stat that shows how many threads are currently trying to add to the > queue. The throttle logic can cause a large number of thread to be blocked. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9074) CacheClientProxyStatistics messageQueueSize does not increase as events are added
[ https://issues.apache.org/jira/browse/GEODE-9074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401766#comment-17401766 ] ASF subversion and git services commented on GEODE-9074: Commit a10a56f573e9a4aabf3c5b6e3862539d6dd93b92 in geode's branch refs/heads/expireAuthentication from Mario Ivanac [ https://gitbox.apache.org/repos/asf?p=geode.git;h=a10a56f ] GEODE-9074: Added update of messageQueueSize at putting message to qu… (#6445) * GEODE-9074: Added update of messageQueueSize at putting message to queue. Also added new statistics messagesBeingQueuedInProgress and messagesBeingQueuedTime. > CacheClientProxyStatistics messageQueueSize does not increase as events are > added > - > > Key: GEODE-9074 > URL: https://issues.apache.org/jira/browse/GEODE-9074 > Project: Geode > Issue Type: Bug > Components: client queues >Reporter: Darrel Schneider >Assignee: Mario Ivanac >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > Fix For: 1.15.0 > > > Something I observed is that while a subscription queue was "full" the > default throttling caused geode to only add 10 events/sec to the queue. This > makes sense. But what didn't make sense was that the messageQueueSize did not > change by 10 events/sec even though, during this time, nothing was draining > from the queue. Then when the draining finally started (because the > CacheClientUpdater started running after a long register interest that had > been blocking it) we saw a huge spike in messageQueueSize when we should have > seen gradual growth. > In addition to improving messageQueueSize it would also be nice to have a > gauge stat that shows how many threads are currently trying to add to the > queue. The throttle logic can cause a large number of thread to be blocked. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9500) RedisData keeps DeltaInfo references too long
[ https://issues.apache.org/jira/browse/GEODE-9500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401773#comment-17401773 ] ASF subversion and git services commented on GEODE-9500: Commit 2a321cf818adae6c8399e8f407d45b17db1eb669 in geode's branch refs/heads/expireAuthentication from Darrel Schneider [ https://gitbox.apache.org/repos/asf?p=geode.git;h=2a321cf ] GEODE-9500: clear deltaInfo even if delta not distributed -- deltaInfo is now cleared right after region.put is called (#6760) -- the size tests no longer clear it -- the unit tests for delta needed to change because the deltaInfo is now cleared earlier > RedisData keeps DeltaInfo references too long > - > > Key: GEODE-9500 > URL: https://issues.apache.org/jira/browse/GEODE-9500 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > The current implementation of Delta for RedisData does not clear the > reference to the DeltaInfo until toDelta is called. This works fine in the > normal case but in the abnormal case it can case extra memory to be used by > the DeltaInfo instances being kept alive. > What can happen is that if the extra server goes down so that geode is > running with one server then some optimization are done by geode and it never > calls toDelta. So in that case the DeltaInfo instances will be kept stored on > the primary. > We actually have sizing tests that found this problem but those tests were > changes to clear the DeltaInfo reference in the test. > Instead we should have these tests not clear it and change geode to clear it > in AbstractRedisData.storeChanges after the put returns. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8870) Remove obsolete version compatibility code
[ https://issues.apache.org/jira/browse/GEODE-8870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401772#comment-17401772 ] ASF subversion and git services commented on GEODE-8870: Commit 6e7110f1cc5a6abe525237dfdfeede7ab459b5f1 in geode's branch refs/heads/expireAuthentication from Jacob Barrett [ https://gitbox.apache.org/repos/asf?p=geode.git;h=6e7110f ] GEODE-8870: Removes GFE_8009 > Remove obsolete version compatibility code > -- > > Key: GEODE-8870 > URL: https://issues.apache.org/jira/browse/GEODE-8870 > Project: Geode > Issue Type: Improvement >Reporter: Jacob Barrett >Assignee: Jacob Barrett >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > As a followup to GEODE-8837 remove all obsolete backwards compatibility code. > This ticket will catch all changes to remove the obsolete code. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9456) Create AuthenticationExpiredException and have the client handle that exception for re-authentication
[ https://issues.apache.org/jira/browse/GEODE-9456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401775#comment-17401775 ] ASF subversion and git services commented on GEODE-9456: Commit 4be645bccc9fed0fe8e796b0f9a9d3ff2437afff in geode's branch refs/heads/expireAuthentication from Jinmei Liao [ https://gitbox.apache.org/repos/asf?p=geode.git;h=4be645b ] GEODE-9456, GEODE-9452: Authentication Expiration (#6721) * Add tests and throw AuthenticationExpiredException Co-authored-by: Joris Melchior > Create AuthenticationExpiredException and have the client handle that > exception for re-authentication > - > > Key: GEODE-9456 > URL: https://issues.apache.org/jira/browse/GEODE-9456 > Project: Geode > Issue Type: Sub-task > Components: core, security >Reporter: Jinmei Liao >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > > Create AuthenticationExpiredException and have the client handle that > exception for re-authentication > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9496) Enhance the usage of newly introduced system property
[ https://issues.apache.org/jira/browse/GEODE-9496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401771#comment-17401771 ] ASF subversion and git services commented on GEODE-9496: Commit 12e0b14e7be01e0fef7abcf5ab50c98f5df2a2d3 in geode's branch refs/heads/expireAuthentication from Xiaojian Zhou [ https://gitbox.apache.org/repos/asf?p=geode.git;h=12e0b14 ] GEODE-9496: Enhance the usage of newly introduced system property (#6756) > Enhance the usage of newly introduced system property > - > > Key: GEODE-9496 > URL: https://issues.apache.org/jira/browse/GEODE-9496 > Project: Geode > Issue Type: Bug >Reporter: Xiaojian Zhou >Priority: Major > Labels: pull-request-available > > In GEODE-9346, I introduced a new system property > enableQueryRetryOnPdxSerializationException in hard-coded way. > We can use SystemPropertyHelper to avoid hard-coded usage. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9184) Implement ZLEXCOUNT Command
[ https://issues.apache.org/jira/browse/GEODE-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401774#comment-17401774 ] ASF subversion and git services commented on GEODE-9184: Commit 7835dc65c4901af38955ca466d098e3ebaed2463 in geode's branch refs/heads/expireAuthentication from Jens Deppe [ https://gitbox.apache.org/repos/asf?p=geode.git;h=7835dc6 ] GEODE-9184: Add Radish ZLEXCOUNT command (#6735) > Implement ZLEXCOUNT Command > --- > > Key: GEODE-9184 > URL: https://issues.apache.org/jira/browse/GEODE-9184 > Project: Geode > Issue Type: New Feature > Components: redis >Reporter: Wayne >Priority: Major > Labels: blocks-1.15.0, pull-request-available, redis > Fix For: 1.15.0 > > > Implement the [ZLEXCOUNT|https://redis.io/commands/zlexcount] command. > > +Acceptance Criteria+ > The ZLEXCOUNT command has been implemented and unit tests are added to ensure > the command works as expected. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9452) The older version client should receive the AuthenticationRequiredException when authentication expires
[ https://issues.apache.org/jira/browse/GEODE-9452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401776#comment-17401776 ] ASF subversion and git services commented on GEODE-9452: Commit 4be645bccc9fed0fe8e796b0f9a9d3ff2437afff in geode's branch refs/heads/expireAuthentication from Jinmei Liao [ https://gitbox.apache.org/repos/asf?p=geode.git;h=4be645b ] GEODE-9456, GEODE-9452: Authentication Expiration (#6721) * Add tests and throw AuthenticationExpiredException Co-authored-by: Joris Melchior > The older version client should receive the AuthenticationRequiredException > when authentication expires > --- > > Key: GEODE-9452 > URL: https://issues.apache.org/jira/browse/GEODE-9452 > Project: Geode > Issue Type: Sub-task > Components: core, security >Reporter: Jinmei Liao >Priority: Major > Labels: GeodeOperationAPI > > Currently, for older client, it's receiving a ClassNotFoundException, we need > to add the serialization code to convert the AuthenticationExpiredException > into this old exception type that the older clients can understand. > > Note: when converting the exception, if we have the message to match what the > older client expects, it can do re-authentication automatically, but we lost > the original message that server has thrown. (Need to consult the PM on what > kind of behavior they want). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9523) ContainerInstall Resource path invalid on Windows
[
https://issues.apache.org/jira/browse/GEODE-9523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-9523:
--
Labels: pull-request-available (was: )
> ContainerInstall Resource path invalid on Windows
> -
>
> Key: GEODE-9523
> URL: https://issues.apache.org/jira/browse/GEODE-9523
> Project: Geode
> Issue Type: Test
> Components: tests
>Reporter: Dale Emery
>Priority: Major
> Labels: pull-request-available
>
> The {{ContainerInstall}} test helper creates an installer using this code:
> {noformat}
> String resource = getResource(getClass(), "/" + downloadURL).getPath();
> URL url = Paths.get(resource).toUri().toURL();
> Installer installer = new ZipURLInstaller(url, TMP_DIR + "/downloads",
> installDir);
> {noformat}
> On Windows, the {{resource}} string is not a valid {{Path}}, and the second
> line throws an exception:
> _java.nio.file.InvalidPathException: Illegal char <:> at index 2:
> /C:/Users/geode/geode/geode-assembly/build/resources/distributedTest/tomcat-9.0.48.zip_
> The chain of conversions is unnecessary. On Windows, the URL returned from
> {{getResource(...)}} is a perfectly fine URL to pass to the
> {{ZipURLInstaller}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9523) ContainerInstall Resource path invalid on Windows
[
https://issues.apache.org/jira/browse/GEODE-9523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dale Emery updated GEODE-9523:
--
Labels: GeodeOperationAPI pull-request-available (was:
pull-request-available)
> ContainerInstall Resource path invalid on Windows
> -
>
> Key: GEODE-9523
> URL: https://issues.apache.org/jira/browse/GEODE-9523
> Project: Geode
> Issue Type: Test
> Components: tests
>Reporter: Dale Emery
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
>
> The {{ContainerInstall}} test helper creates an installer using this code:
> {noformat}
> String resource = getResource(getClass(), "/" + downloadURL).getPath();
> URL url = Paths.get(resource).toUri().toURL();
> Installer installer = new ZipURLInstaller(url, TMP_DIR + "/downloads",
> installDir);
> {noformat}
> On Windows, the {{resource}} string is not a valid {{Path}}, and the second
> line throws an exception:
> _java.nio.file.InvalidPathException: Illegal char <:> at index 2:
> /C:/Users/geode/geode/geode-assembly/build/resources/distributedTest/tomcat-9.0.48.zip_
> The chain of conversions is unnecessary. On Windows, the URL returned from
> {{getResource(...)}} is a perfectly fine URL to pass to the
> {{ZipURLInstaller}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-9523) ContainerInstall Resource path invalid on Windows
[
https://issues.apache.org/jira/browse/GEODE-9523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dale Emery reassigned GEODE-9523:
-
Assignee: Dale Emery
> ContainerInstall Resource path invalid on Windows
> -
>
> Key: GEODE-9523
> URL: https://issues.apache.org/jira/browse/GEODE-9523
> Project: Geode
> Issue Type: Test
> Components: tests
>Reporter: Dale Emery
>Assignee: Dale Emery
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
>
> The {{ContainerInstall}} test helper creates an installer using this code:
> {noformat}
> String resource = getResource(getClass(), "/" + downloadURL).getPath();
> URL url = Paths.get(resource).toUri().toURL();
> Installer installer = new ZipURLInstaller(url, TMP_DIR + "/downloads",
> installDir);
> {noformat}
> On Windows, the {{resource}} string is not a valid {{Path}}, and the second
> line throws an exception:
> _java.nio.file.InvalidPathException: Illegal char <:> at index 2:
> /C:/Users/geode/geode/geode-assembly/build/resources/distributedTest/tomcat-9.0.48.zip_
> The chain of conversions is unnecessary. On Windows, the URL returned from
> {{getResource(...)}} is a perfectly fine URL to pass to the
> {{ZipURLInstaller}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9515) MBeanServer object already initialized with LocatorLauncher and JMX Manager Access File
[
https://issues.apache.org/jira/browse/GEODE-9515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-9515:
--
Labels: GeodeOperationAPI pull-request-available (was: GeodeOperationAPI)
> MBeanServer object already initialized with LocatorLauncher and JMX Manager
> Access File
> ---
>
> Key: GEODE-9515
> URL: https://issues.apache.org/jira/browse/GEODE-9515
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.12.4
>Reporter: Jianxia Chen
>Assignee: Jianxia Chen
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
>
> When starting a locator with LocatorLauncher with JMX manager access file,
> the following exception shows up:
> {code}
> ERROR SystemManagementService Jmx manager could not be started because
> MBeanServer object already initialized
> java.lang.IllegalArgumentException: MBeanServer object already initialized
> at
> com.sun.jmx.remote.security.MBeanServerAccessController.setMBeanServer(MBeanServerAccessController.java:97)
> at
> javax.management.remote.JMXConnectorServer.setMBeanServerForwarder(JMXConnectorServer.java:119)
> at
> javax.management.remote.rmi.RMIConnectorServer.setMBeanServerForwarder(RMIConnectorServer.java:597)
> at
> org.apache.geode.management.internal.ManagementAgent.configureAndStart(ManagementAgent.java:441)
> at
> org.apache.geode.management.internal.ManagementAgent.startAgent(ManagementAgent.java:139)
> at
> org.apache.geode.management.internal.SystemManagementService.startManager(SystemManagementService.java:378)
> at
> org.apache.geode.management.internal.beans.ManagementAdapter.handleCacheCreation(ManagementAdapter.java:197)
> at
> org.apache.geode.management.internal.beans.ManagementListener.handleEvent(ManagementListener.java:127)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.notifyResourceEventListeners(InternalDistributedSystem.java:2089)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.handleResourceEvent(InternalDistributedSystem.java:643)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1363)
> at
> org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:191)
> at
> org.apache.geode.distributed.internal.InternalLocator.startCache(InternalLocator.java:766)
> at
> org.apache.geode.distributed.internal.InternalLocator.startDistributedSystem(InternalLocator.java:755)
> at
> org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:386)
> at
> org.apache.geode.distributed.LocatorLauncher.start(LocatorLauncher.java:714)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9302) Benchmark instability in PartitionedPutStringBenchmark
[
https://issues.apache.org/jira/browse/GEODE-9302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401795#comment-17401795
]
Ray Ingles commented on GEODE-9302:
---
(Note that for [benchmark-base
#128|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/benchmark-base/builds/128],
there may have been other issues with this run.)
> Benchmark instability in PartitionedPutStringBenchmark
> --
>
> Key: GEODE-9302
> URL: https://issues.apache.org/jira/browse/GEODE-9302
> Project: Geode
> Issue Type: Bug
> Components: benchmarks
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Priority: Major
>
> A benchmark failure due to the recently-introduced
> PartitionedPutStringBenchmark was observed:
> {noformat}
> This is ITERATION 1 of benchmarking against baseline.
> P2pPartitionedGetBenchmark avg ops/sec
> Baseline:853001.60 Test:867151.67 Difference: +1.7%
> avg latency
> Baseline:842007.55 Test:828545.06 Difference: -1.6%
> P2pPartitionedPutBenchmark avg ops/sec
> Baseline:128283.47 Test:126510.92 Difference: -1.4%
> avg latency
> Baseline: 5785619.62 Test: 5915913.49 Difference: +2.3%
> P2pPartitionedPutBytesBenchmark avg ops/sec
> Baseline:175658.08 Test:174865.97 Difference: -0.5%
> avg latency
> Baseline: 4130071.43 Test: 4130753.09 Difference: +0.0%
>PartitionedFunctionExecutionBenchmark avg ops/sec
> Baseline:254788.26 Test:268132.99 Difference: +5.2%
> avg latency
> Baseline:846158.41 Test:804199.42 Difference: -5.0%
> PartitionedFunctionExecutionWithArgumentsBenchmark avg ops/sec
> Baseline:278669.87 Test:281504.58 Difference: +1.0%
> avg latency
> Baseline: 1031826.82 Test: 1021314.54 Difference: -1.0%
> PartitionedFunctionExecutionWithFiltersBenchmark avg ops/sec
> Baseline:372204.82 Test:348815.81 Difference: -6.3%
> avg latency
> Baseline: 1545217.38 Test: 1649706.37 Difference: +6.8%
> PartitionedGetBenchmark avg ops/sec
> Baseline:823740.09 Test:819044.99 Difference: -0.6%
> avg latency
> Baseline:872172.75 Test:877580.02 Difference: +0.6%
> PartitionedGetLongBenchmark avg ops/sec
> Baseline: 1047221.43 Test: 1045565.89 Difference: -0.2%
> avg latency
> Baseline:685757.55 Test:687005.43 Difference: +0.2%
>PartitionedGetStringBenchmark avg ops/sec
> Baseline: 1055904.14 Test: 1045420.73 Difference: -1.0%
> avg latency
> Baseline:680031.44 Test:687045.15 Difference: +1.0%
> PartitionedIndexedQueryBenchmark avg ops/sec
> Baseline: 31596.35 Test: 31653.48 Difference: +0.2%
> avg latency
> Baseline: 18221302.10 Test: 18216097.86 Difference: -0.0%
> PartitionedNonIndexedQueryBenchmark avg ops/sec
> Baseline:95.78 Test: 100.35 Difference: +4.8%
> avg latency
> Baseline: 750871203.78 Test: 716853923.95 Difference: -4.5%
> PartitionedPutAllBenchmark avg ops/sec
> Baseline: 8675.75 Test: 8628.10 Difference: -0.5%
> avg latency
> Baseline: 16595044.73 Test: 16685258.91 Difference: +0.5%
> PartitionedPutAllLongBenchmark avg ops/sec
> Baseline: 1382.38 Test: 1380.50 Difference: -0.1%
> avg latency
> Baseline: 104866853.92 Test: 104775538.34 Difference: -0.1%
> PartitionedPutBenchmark avg ops/sec
> Baseline:491790.40 Test:479926.75 Difference: -2.4%
> avg latency
> Baseline: 1461947.23 Test:
[jira] [Commented] (GEODE-8980) bump dependencies for 1.15.0 [PERMANENT]
[ https://issues.apache.org/jira/browse/GEODE-8980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401806#comment-17401806 ] ASF subversion and git services commented on GEODE-8980: Commit 76695e405ac2e3f0448c3a013208db750bb6c720 in geode's branch refs/heads/develop from Owen Nichols [ https://gitbox.apache.org/repos/asf?p=geode.git;h=76695e4 ] GEODE-8980: bump deps (#6734) * Bump classgraph from 4.8.109 to 4.8.110 * Bump commons-io from 2.10.0 to 2.11.0 * Bump jedis from 3.6.1 to 3.6.3 * Bump jetty from 9.4.42.v20210604 to 9.4.43.v20210629 * Bump lettuce-core from 6.1.3.RELEASE to 6.1.4.RELEASE * Bump micrometer-core from 1.7.1 to 1.7.2 * Bump mysql-connector-java from 8.0.25 to 8.0.26 * Bump spring from 5.3.8 to 5.3.9 * Bump spring-boot-starter from 2.5.2 to 2.5.3 * Bump spring-hateoas from 1.3.2 to 1.3.3 * Bump tomcat from 9.0.48 to 9.0.50 > bump dependencies for 1.15.0 [PERMANENT] > > > Key: GEODE-8980 > URL: https://issues.apache.org/jira/browse/GEODE-8980 > Project: Geode > Issue Type: Improvement > Components: build >Affects Versions: 1.15.0 >Reporter: Owen Nichols >Priority: Major > Labels: pull-request-available > > keeping up with the latest versions of 3rd-party libraries used by Geode is a > proactive way to reduce bugs and avoid security vulnerabilities. this ticket > will be used for ~monthly dependency bumps on develop until we get close to > cutting support/1.15 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9524) Make name of directory agree with library name for C bindings
Blake Bender created GEODE-9524: --- Summary: Make name of directory agree with library name for C bindings Key: GEODE-9524 URL: https://issues.apache.org/jira/browse/GEODE-9524 Project: Geode Issue Type: Improvement Components: native client Reporter: Blake Bender Path uses c_bindings with a `_`, but the library is c-bindings with a `-`. Switch to `-` everywhere for consistency. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9524) Make name of directory agree with library name for C bindings
[ https://issues.apache.org/jira/browse/GEODE-9524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Bender updated GEODE-9524: Description: Path uses c_bindings with a '_', but the library is c-bindings with a '-'. Switch to '-' everywhere for consistency. (was: Path uses c_bindings with a `_`, but the library is c-bindings with a `-`. Switch to `-` everywhere for consistency.) > Make name of directory agree with library name for C bindings > - > > Key: GEODE-9524 > URL: https://issues.apache.org/jira/browse/GEODE-9524 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Priority: Major > > Path uses c_bindings with a '_', but the library is c-bindings with a '-'. > Switch to '-' everywhere for consistency. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9524) Make name of directory agree with library name for C bindings
[ https://issues.apache.org/jira/browse/GEODE-9524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Bender updated GEODE-9524: Description: Path uses c_bindings with a '_', but the library is c-bindings with a "-". Switch to "-" everywhere for consistency. (was: Path uses c_bindings with a '_', but the library is c-bindings with a '-'. Switch to '-' everywhere for consistency.) > Make name of directory agree with library name for C bindings > - > > Key: GEODE-9524 > URL: https://issues.apache.org/jira/browse/GEODE-9524 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Priority: Major > > Path uses c_bindings with a '_', but the library is c-bindings with a "-". > Switch to "-" everywhere for consistency. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-9499) RedisData does not need an object reference to implement Delta
[ https://issues.apache.org/jira/browse/GEODE-9499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ray Ingles reassigned GEODE-9499: - Assignee: Ray Ingles > RedisData does not need an object reference to implement Delta > -- > > Key: GEODE-9499 > URL: https://issues.apache.org/jira/browse/GEODE-9499 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: Darrel Schneider >Assignee: Ray Ingles >Priority: Major > > Currently every redis data structure implements the RedisData interface. Part > of that implementation is Delta support. The way it is implemented is by > storing a reference to a DeltaInfo instance in each RedisData. Most of the > time this reference is null but it still takes up 8 bytes (4 if oops are > compressed). It is only non-null while an update is in progress. > What we could do instead is store the reference to the DeltaInfo in a thread > local. That works because we are careful to run each redis command that > modifies a RedisData on the primary. We lock the primary down during the > operation to prevent it from moving. So when it comes time for the primary to > call toDelta on the RedisData instance to distribute it to the secondary, > this call will done on the same thread so our hasDelta and toDelta can just > read the ThreadLocal. This will save us one object reference for every > redis key we store. > Something else we could consider doing is to pass the DeltaInfo as the > callback arg when we do the region put. But this would require change to core > geode to detect that the callback arg is a DeltaInfo and to use it to compute > the delta bytes that are stored on the EntryEventImpl. This is doable and may > even perform better but would require changes to the core. It would probably > be a bit faster than the ThreadLocal solution just because of the extra > latency in setting and reading a ThreadLocal compared to a stack parameter -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9524) Make name of directory agree with library name for C bindings
[ https://issues.apache.org/jira/browse/GEODE-9524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Bender resolved GEODE-9524. - Fix Version/s: 1.15.0 Resolution: Fixed > Make name of directory agree with library name for C bindings > - > > Key: GEODE-9524 > URL: https://issues.apache.org/jira/browse/GEODE-9524 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > Path uses c_bindings with a '_', but the library is c-bindings with a "-". > Switch to "-" everywhere for consistency. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9524) Make name of directory agree with library name for C bindings
[ https://issues.apache.org/jira/browse/GEODE-9524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-9524: -- Labels: pull-request-available (was: ) > Make name of directory agree with library name for C bindings > - > > Key: GEODE-9524 > URL: https://issues.apache.org/jira/browse/GEODE-9524 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Priority: Major > Labels: pull-request-available > > Path uses c_bindings with a '_', but the library is c-bindings with a "-". > Switch to "-" everywhere for consistency. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9524) Make name of directory agree with library name for C bindings
[ https://issues.apache.org/jira/browse/GEODE-9524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401829#comment-17401829 ] ASF subversion and git services commented on GEODE-9524: Commit 5d3590c27678a411ec6a057f14fa6ee7dcec908e in geode-native's branch refs/heads/develop from Blake Bender [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=5d3590c ] GEODE-9524: Make library name and directory name consistent (#853) Co-authored-by: Matthew Reddington > Make name of directory agree with library name for C bindings > - > > Key: GEODE-9524 > URL: https://issues.apache.org/jira/browse/GEODE-9524 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Priority: Major > > Path uses c_bindings with a '_', but the library is c-bindings with a "-". > Switch to "-" everywhere for consistency. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (GEODE-9524) Make name of directory agree with library name for C bindings
[ https://issues.apache.org/jira/browse/GEODE-9524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Bender closed GEODE-9524. --- > Make name of directory agree with library name for C bindings > - > > Key: GEODE-9524 > URL: https://issues.apache.org/jira/browse/GEODE-9524 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > Path uses c_bindings with a '_', but the library is c-bindings with a "-". > Switch to "-" everywhere for consistency. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9524) Make name of directory agree with library name for C bindings
[ https://issues.apache.org/jira/browse/GEODE-9524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401830#comment-17401830 ] ASF GitHub Bot commented on GEODE-9524: --- pdxcodemonkey merged pull request #853: URL: https://github.com/apache/geode-native/pull/853 -- 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 > Make name of directory agree with library name for C bindings > - > > Key: GEODE-9524 > URL: https://issues.apache.org/jira/browse/GEODE-9524 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Priority: Major > > Path uses c_bindings with a '_', but the library is c-bindings with a "-". > Switch to "-" everywhere for consistency. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9525) Add Radish benchmark tests to CI
Jens Deppe created GEODE-9525: - Summary: Add Radish benchmark tests to CI Key: GEODE-9525 URL: https://issues.apache.org/jira/browse/GEODE-9525 Project: Geode Issue Type: Test Components: redis Reporter: Jens Deppe -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-9446) Remove unnecessary uses of byte[] in RedisSortedSet
[
https://issues.apache.org/jira/browse/GEODE-9446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hale Bales reassigned GEODE-9446:
-
Assignee: Hale Bales
> Remove unnecessary uses of byte[] in RedisSortedSet
> ---
>
> Key: GEODE-9446
> URL: https://issues.apache.org/jira/browse/GEODE-9446
> Project: Geode
> Issue Type: Improvement
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Assignee: Hale Bales
>Priority: Major
>
> The current implementation of {{RedisSortedSet}} uses an
> {{AbstractOrderedStatisticsEntry}} class containing both {{double}} score and
> {{byte[]}} scoreBytes fields. The {{double}} field is required to allow the
> sorting behaviour required of the data structure, but the {{byte[]}} field is
> not necessary except when returning results to the client.
> The class should be refactored to eliminate the {{byte[]}} scoreBytes field
> from {{AbstractOrderedStatisticsEntry}} and reduce the memory overhead of
> operations.
> As part of this refactoring, the below call to {{members.put()}} should be
> removed from {{memberAdd()}} as it will no longer be necessary.
> {code:java}
> protected synchronized byte[] memberAdd(byte[] memberToAdd, byte[]
> scoreToAdd) {
> ...
> } else {
> scoreSet.remove(existingEntry);
> byte[] oldScore = existingEntry.scoreBytes;
> existingEntry.updateScore(stripTrailingZeroFromDouble(scoreToAdd));
> members.put(memberToAdd, existingEntry); <<< remove this
> scoreSet.add(existingEntry);
> return oldScore;
> }
> {code}
> Also, uses of the {{stripTrailingZeroFromDouble()}} method should be moved to
> just prior to the response being returned to the client, to ensure that the
> format of the returned String representations of double values match native
> Redis.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9525) Add Radish benchmark tests to CI
[ https://issues.apache.org/jira/browse/GEODE-9525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-9525: -- Labels: pull-request-available (was: ) > Add Radish benchmark tests to CI > > > Key: GEODE-9525 > URL: https://issues.apache.org/jira/browse/GEODE-9525 > Project: Geode > Issue Type: Test > Components: redis >Reporter: Jens Deppe >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9071) CI Failure: PartitionedRegionCqQueryDUnitTest > testRemoveAllWithCQLocalDestroy
[
https://issues.apache.org/jira/browse/GEODE-9071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401850#comment-17401850
]
Geode Integration commented on GEODE-9071:
--
Seen in [distributed-test-openjdk8
#130|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/distributed-test-openjdk8/builds/130]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0420/test-results/distributedTest/1629399600/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0420/test-artifacts/1629399600/distributedtestfiles-openjdk8-1.15.0-build.0420.tgz].
> CI Failure: PartitionedRegionCqQueryDUnitTest >
> testRemoveAllWithCQLocalDestroy
> ---
>
> Key: GEODE-9071
> URL: https://issues.apache.org/jira/browse/GEODE-9071
> Project: Geode
> Issue Type: Bug
> Components: cq
>Affects Versions: 1.12.3, 1.13.3, 1.14.0, 1.15.0
>Reporter: Jens Deppe
>Priority: Major
> Labels: caching-applications
>
> {noformat}
> org.apache.geode.cache.query.cq.dunit.PartitionedRegionCqQueryDUnitTest >
> testRemoveAllWithCQLocalDestroy FAILED
> 10:10:22org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache.query.cq.dunit.PartitionedRegionCqQueryDUnitTest$$Lambda$87/434016892.run
> in VM 2 running on Host bb8c1d338b8b with 4 VMs
> 10:10:22at
> org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
> 10:10:22at org.apache.geode.test.dunit.VM.invoke(VM.java:448)
> 10:10:22at
> org.apache.geode.cache.query.cq.dunit.PartitionedRegionCqQueryDUnitTest.testRemoveAllWithCQLocalDestroy(PartitionedRegionCqQueryDUnitTest.java:243)
> 10:10:22
> 10:10:22Caused by:
> 10:10:22org.junit.ComparisonFailure: expected:<[999]> but was:<[645]>
> 10:10:22at
> sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> 10:10:22at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> 10:10:22at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> 10:10:22at
> org.apache.geode.cache.query.cq.dunit.PartitionedRegionCqQueryDUnitTest.lambda$testRemoveAllWithCQLocalDestroy$c93719d5$3(PartitionedRegionCqQueryDUnitTest.java:251)
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0082/test-results/distributedTest/1616696789/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0082/test-artifacts/1616696789/distributedtestfiles-OpenJDK8-1.15.0-build.0082.tgz
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-4181) Update to JUnit 5.x
[ https://issues.apache.org/jira/browse/GEODE-4181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401861#comment-17401861 ] ASF subversion and git services commented on GEODE-4181: Commit 5e9b3684f2be3f2ff8174c690bd2c15d31f9179c in geode's branch refs/heads/develop from Dale Emery [ https://gitbox.apache.org/repos/asf?p=geode.git;h=5e9b368 ] GEODE-4181: Reduce ChildVM command line length (#6763) PROBLEM Windows limits command lines to a maximum length of ~32k characters. The command line for DUnit child VMs is very close to this limit. Currently this prevents us from adding JUnit 5 support. JUnit 5 adds 8 more jars to the classpath, which adds ~1300 characters to the command line, which puts the command line over the limit. SOLUTION Write the ChildVM's entire classpath to a "pathing" jar, then include only that pathing jar on the command line. This results in command line that is shorter by many thousands of characters, and which does not grow as we add more jars or other classpath elements. > Update to JUnit 5.x > --- > > Key: GEODE-4181 > URL: https://issues.apache.org/jira/browse/GEODE-4181 > Project: Geode > Issue Type: Improvement > Components: general, tests >Reporter: Patrick Rhomberg >Assignee: Dale Emery >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > > In addition to the expected benefits that come with new versions, updating to > JUnit 5.x should allow us to remove the workaround required in GEODE-1350 / > GEODE-4122. > If migration guides are to be believed, migration from JUnit 4.x to 5.x in > and of itself should not be difficult. However, interaction with Mockito and > PowerMock appears to be significantly different and will require > investigation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-9436) Implement ZREMRANGEBYSCORE Command
[ https://issues.apache.org/jira/browse/GEODE-9436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donal Evans reassigned GEODE-9436: -- Assignee: Donal Evans > Implement ZREMRANGEBYSCORE Command > -- > > Key: GEODE-9436 > URL: https://issues.apache.org/jira/browse/GEODE-9436 > Project: Geode > Issue Type: New Feature > Components: redis >Reporter: Wayne >Assignee: Donal Evans >Priority: Major > > Implement the [ZREMRANGEBYSCORE|https://redis.io/commands/zremrangebyscore] > command. > > +Acceptance Criteria+ > > The command has been implemented along with appropriate unit tests. > > The command has been added to the AbstractHitsMissesIntegrationTest. The > command has been tested using the redis-cli tool and verified against native > redis. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9526) DiskStore test incorrectly treats absolute path as relative on Windows
Dale Emery created GEODE-9526:
-
Summary: DiskStore test incorrectly treats absolute path as
relative on Windows
Key: GEODE-9526
URL: https://issues.apache.org/jira/browse/GEODE-9526
Project: Geode
Issue Type: Test
Components: tests
Reporter: Dale Emery
On Windows, an absolute file path can begin with a letter (e.g. "C:\…").
{{DiskStoreCommandsDUnitTest.verifyDiskStoreInServer(...)}} incorrectly assumes
that, because such a path does not start with a file separator, it must be
relative. It then attempts to convert it to an absolute path by prepending the
current directory onto it:
{noformat}
String absoluteDiskDirectoryName = diskDirectoryName.startsWith(File.separator)
? diskDirectoryName
: CURRENT_DIRECTORY + File.separator + diskDirectoryName;
{noformat}
On Windows, the resulting file path is unusable.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-9527) SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
Owen Nichols created GEODE-9527:
---
Summary: SSLTest > driverCannotConnectIfProtocolsMismatch fails
often on JDK 11.0.12
Key: GEODE-9527
URL: https://issues.apache.org/jira/browse/GEODE-9527
Project: Geode
Issue Type: Bug
Components: membership
Affects Versions: 1.13.4, 1.12.4, 1.14.0
Reporter: Owen Nichols
This fails the most on Windows, but also on Linux. It seems to happen much
more on 1.12 and 1.13, but also seen on 1.14. However not seen on develop...so
maybe there is some fix already that just needs to be backported? If so please
close this as a dupe.
{noformat}
org.apache.geode.experimental.driver.SSLTest >
driverCannotConnectIfProtocolsMismatch FAILED
java.lang.AssertionError:
Expected: an instance of javax.net.ssl.SSLException
but: is a
java.net.SocketException
Stacktrace was: java.net.SocketException: Connection reset
at java.base/java.net.SocketInputStream.read(SocketInputStream.java:186)
at java.base/java.net.SocketInputStream.read(SocketInputStream.java:140)
at
java.base/sun.security.ssl.SSLSocketInputRecord.read(SSLSocketInputRecord.java:478)
at
java.base/sun.security.ssl.SSLSocketInputRecord.readHeader(SSLSocketInputRecord.java:472)
at
java.base/sun.security.ssl.SSLSocketInputRecord.decode(SSLSocketInputRecord.java:160)
at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:111)
at
java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1426)
at
java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1336)
at
java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:450)
at
java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:421)
at
org.apache.geode.experimental.driver.SocketFactory.connect(SocketFactory.java:146)
at
org.apache.geode.experimental.driver.ProtobufChannel.createSocket(ProtobufChannel.java:232)
at
org.apache.geode.experimental.driver.ProtobufChannel.findAServer(ProtobufChannel.java:116)
at
org.apache.geode.experimental.driver.ProtobufChannel.connectToAServer(ProtobufChannel.java:66)
at
org.apache.geode.experimental.driver.ProtobufChannel.(ProtobufChannel.java:49)
at
org.apache.geode.experimental.driver.ProtobufDriver.(ProtobufDriver.java:60)
at
org.apache.geode.experimental.driver.DriverFactory.create(DriverFactory.java:154)
at
org.apache.geode.experimental.driver.SSLTest.driverCannotConnectIfProtocolsMismatch(SSLTest.java:190)
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9527) SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
[
https://issues.apache.org/jira/browse/GEODE-9527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401900#comment-17401900
]
Geode Integration commented on GEODE-9527:
--
Seen on support/1.13 in [integration-test-openjdk11
#32|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-main/jobs/integration-test-openjdk11/builds/32]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.5-build.0573/test-results/integrationTest/1628671936/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.5-build.0573/test-artifacts/1628671936/integrationtestfiles-openjdk11-1.13.5-build.0573.tgz].
> SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
> ---
>
> Key: GEODE-9527
> URL: https://issues.apache.org/jira/browse/GEODE-9527
> Project: Geode
> Issue Type: Bug
> Components: membership
>Affects Versions: 1.12.4, 1.13.4, 1.14.0
>Reporter: Owen Nichols
>Priority: Major
> Labels: blocks-1.12.5, blocks-1.13.5, blocks-1.14.0
>
> This fails the most on Windows, but also on Linux. It seems to happen much
> more on 1.12 and 1.13, but also seen on 1.14. However not seen on
> develop...so maybe there is some fix already that just needs to be
> backported? If so please close this as a dupe.
> {noformat}
> org.apache.geode.experimental.driver.SSLTest >
> driverCannotConnectIfProtocolsMismatch FAILED
> java.lang.AssertionError:
> Expected: an instance of javax.net.ssl.SSLException
> but: is a
> java.net.SocketException
> Stacktrace was: java.net.SocketException: Connection reset
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:186)
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:140)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.read(SSLSocketInputRecord.java:478)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.readHeader(SSLSocketInputRecord.java:472)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.decode(SSLSocketInputRecord.java:160)
> at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:111)
> at
> java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1426)
> at
> java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1336)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:450)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:421)
> at
> org.apache.geode.experimental.driver.SocketFactory.connect(SocketFactory.java:146)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.createSocket(ProtobufChannel.java:232)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.findAServer(ProtobufChannel.java:116)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.connectToAServer(ProtobufChannel.java:66)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.(ProtobufChannel.java:49)
> at
> org.apache.geode.experimental.driver.ProtobufDriver.(ProtobufDriver.java:60)
> at
> org.apache.geode.experimental.driver.DriverFactory.create(DriverFactory.java:154)
> at
> org.apache.geode.experimental.driver.SSLTest.driverCannotConnectIfProtocolsMismatch(SSLTest.java:190)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9527) SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
[
https://issues.apache.org/jira/browse/GEODE-9527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401899#comment-17401899
]
Geode Integration commented on GEODE-9527:
--
Seen on support/1.12 in [integration-test-openjdk11
#22|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/integration-test-openjdk11/builds/22]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0268/test-results/integrationTest/1628302808/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0268/test-artifacts/1628302808/integrationtestfiles-openjdk11-1.12.5-build.0268.tgz].
> SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
> ---
>
> Key: GEODE-9527
> URL: https://issues.apache.org/jira/browse/GEODE-9527
> Project: Geode
> Issue Type: Bug
> Components: membership
>Affects Versions: 1.12.4, 1.13.4, 1.14.0
>Reporter: Owen Nichols
>Priority: Major
> Labels: blocks-1.12.5, blocks-1.13.5, blocks-1.14.0
>
> This fails the most on Windows, but also on Linux. It seems to happen much
> more on 1.12 and 1.13, but also seen on 1.14. However not seen on
> develop...so maybe there is some fix already that just needs to be
> backported? If so please close this as a dupe.
> {noformat}
> org.apache.geode.experimental.driver.SSLTest >
> driverCannotConnectIfProtocolsMismatch FAILED
> java.lang.AssertionError:
> Expected: an instance of javax.net.ssl.SSLException
> but: is a
> java.net.SocketException
> Stacktrace was: java.net.SocketException: Connection reset
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:186)
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:140)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.read(SSLSocketInputRecord.java:478)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.readHeader(SSLSocketInputRecord.java:472)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.decode(SSLSocketInputRecord.java:160)
> at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:111)
> at
> java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1426)
> at
> java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1336)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:450)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:421)
> at
> org.apache.geode.experimental.driver.SocketFactory.connect(SocketFactory.java:146)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.createSocket(ProtobufChannel.java:232)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.findAServer(ProtobufChannel.java:116)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.connectToAServer(ProtobufChannel.java:66)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.(ProtobufChannel.java:49)
> at
> org.apache.geode.experimental.driver.ProtobufDriver.(ProtobufDriver.java:60)
> at
> org.apache.geode.experimental.driver.DriverFactory.create(DriverFactory.java:154)
> at
> org.apache.geode.experimental.driver.SSLTest.driverCannotConnectIfProtocolsMismatch(SSLTest.java:190)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9527) SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
[
https://issues.apache.org/jira/browse/GEODE-9527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen Nichols updated GEODE-9527:
Labels: blocks-1.12.5 blocks-1.13.5 blocks-1.14.0 (was: )
> SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
> ---
>
> Key: GEODE-9527
> URL: https://issues.apache.org/jira/browse/GEODE-9527
> Project: Geode
> Issue Type: Bug
> Components: membership
>Affects Versions: 1.12.4, 1.13.4, 1.14.0
>Reporter: Owen Nichols
>Priority: Major
> Labels: blocks-1.12.5, blocks-1.13.5, blocks-1.14.0
>
> This fails the most on Windows, but also on Linux. It seems to happen much
> more on 1.12 and 1.13, but also seen on 1.14. However not seen on
> develop...so maybe there is some fix already that just needs to be
> backported? If so please close this as a dupe.
> {noformat}
> org.apache.geode.experimental.driver.SSLTest >
> driverCannotConnectIfProtocolsMismatch FAILED
> java.lang.AssertionError:
> Expected: an instance of javax.net.ssl.SSLException
> but: is a
> java.net.SocketException
> Stacktrace was: java.net.SocketException: Connection reset
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:186)
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:140)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.read(SSLSocketInputRecord.java:478)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.readHeader(SSLSocketInputRecord.java:472)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.decode(SSLSocketInputRecord.java:160)
> at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:111)
> at
> java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1426)
> at
> java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1336)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:450)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:421)
> at
> org.apache.geode.experimental.driver.SocketFactory.connect(SocketFactory.java:146)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.createSocket(ProtobufChannel.java:232)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.findAServer(ProtobufChannel.java:116)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.connectToAServer(ProtobufChannel.java:66)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.(ProtobufChannel.java:49)
> at
> org.apache.geode.experimental.driver.ProtobufDriver.(ProtobufDriver.java:60)
> at
> org.apache.geode.experimental.driver.DriverFactory.create(DriverFactory.java:154)
> at
> org.apache.geode.experimental.driver.SSLTest.driverCannotConnectIfProtocolsMismatch(SSLTest.java:190)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9527) SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
[
https://issues.apache.org/jira/browse/GEODE-9527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401901#comment-17401901
]
Geode Integration commented on GEODE-9527:
--
Seen on support/1.13 in [integration-test-openjdk11
#34|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-main/jobs/integration-test-openjdk11/builds/34]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.5-build.0574/test-results/integrationTest/1628802177/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.5-build.0574/test-artifacts/1628802177/integrationtestfiles-openjdk11-1.13.5-build.0574.tgz].
> SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
> ---
>
> Key: GEODE-9527
> URL: https://issues.apache.org/jira/browse/GEODE-9527
> Project: Geode
> Issue Type: Bug
> Components: membership
>Affects Versions: 1.12.4, 1.13.4, 1.14.0
>Reporter: Owen Nichols
>Priority: Major
> Labels: blocks-1.12.5, blocks-1.13.5, blocks-1.14.0
>
> This fails the most on Windows, but also on Linux. It seems to happen much
> more on 1.12 and 1.13, but also seen on 1.14. However not seen on
> develop...so maybe there is some fix already that just needs to be
> backported? If so please close this as a dupe.
> {noformat}
> org.apache.geode.experimental.driver.SSLTest >
> driverCannotConnectIfProtocolsMismatch FAILED
> java.lang.AssertionError:
> Expected: an instance of javax.net.ssl.SSLException
> but: is a
> java.net.SocketException
> Stacktrace was: java.net.SocketException: Connection reset
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:186)
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:140)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.read(SSLSocketInputRecord.java:478)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.readHeader(SSLSocketInputRecord.java:472)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.decode(SSLSocketInputRecord.java:160)
> at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:111)
> at
> java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1426)
> at
> java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1336)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:450)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:421)
> at
> org.apache.geode.experimental.driver.SocketFactory.connect(SocketFactory.java:146)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.createSocket(ProtobufChannel.java:232)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.findAServer(ProtobufChannel.java:116)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.connectToAServer(ProtobufChannel.java:66)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.(ProtobufChannel.java:49)
> at
> org.apache.geode.experimental.driver.ProtobufDriver.(ProtobufDriver.java:60)
> at
> org.apache.geode.experimental.driver.DriverFactory.create(DriverFactory.java:154)
> at
> org.apache.geode.experimental.driver.SSLTest.driverCannotConnectIfProtocolsMismatch(SSLTest.java:190)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9527) SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
[
https://issues.apache.org/jira/browse/GEODE-9527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401903#comment-17401903
]
Geode Integration commented on GEODE-9527:
--
Seen on support/1.13 in [integration-test-openjdk11
#36|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-main/jobs/integration-test-openjdk11/builds/36]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.5-build.0575/test-results/integrationTest/1628805986/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.5-build.0575/test-artifacts/1628805986/integrationtestfiles-openjdk11-1.13.5-build.0575.tgz].
> SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
> ---
>
> Key: GEODE-9527
> URL: https://issues.apache.org/jira/browse/GEODE-9527
> Project: Geode
> Issue Type: Bug
> Components: membership
>Affects Versions: 1.12.4, 1.13.4, 1.14.0
>Reporter: Owen Nichols
>Priority: Major
> Labels: blocks-1.12.5, blocks-1.13.5, blocks-1.14.0
>
> This fails the most on Windows, but also on Linux. It seems to happen much
> more on 1.12 and 1.13, but also seen on 1.14. However not seen on
> develop...so maybe there is some fix already that just needs to be
> backported? If so please close this as a dupe.
> {noformat}
> org.apache.geode.experimental.driver.SSLTest >
> driverCannotConnectIfProtocolsMismatch FAILED
> java.lang.AssertionError:
> Expected: an instance of javax.net.ssl.SSLException
> but: is a
> java.net.SocketException
> Stacktrace was: java.net.SocketException: Connection reset
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:186)
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:140)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.read(SSLSocketInputRecord.java:478)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.readHeader(SSLSocketInputRecord.java:472)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.decode(SSLSocketInputRecord.java:160)
> at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:111)
> at
> java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1426)
> at
> java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1336)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:450)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:421)
> at
> org.apache.geode.experimental.driver.SocketFactory.connect(SocketFactory.java:146)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.createSocket(ProtobufChannel.java:232)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.findAServer(ProtobufChannel.java:116)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.connectToAServer(ProtobufChannel.java:66)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.(ProtobufChannel.java:49)
> at
> org.apache.geode.experimental.driver.ProtobufDriver.(ProtobufDriver.java:60)
> at
> org.apache.geode.experimental.driver.DriverFactory.create(DriverFactory.java:154)
> at
> org.apache.geode.experimental.driver.SSLTest.driverCannotConnectIfProtocolsMismatch(SSLTest.java:190)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9527) SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
[
https://issues.apache.org/jira/browse/GEODE-9527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401907#comment-17401907
]
Geode Integration commented on GEODE-9527:
--
Seen on support/1.12 in [windows-integration-test-openjdk11
#24|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/windows-integration-test-openjdk11/builds/24]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0270/test-results/integrationTest/1628849805/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0270/test-artifacts/1628849805/windows-integrationtestfiles-openjdk11-1.12.5-build.0270.tgz].
> SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
> ---
>
> Key: GEODE-9527
> URL: https://issues.apache.org/jira/browse/GEODE-9527
> Project: Geode
> Issue Type: Bug
> Components: membership
>Affects Versions: 1.12.4, 1.13.4, 1.14.0
>Reporter: Owen Nichols
>Priority: Major
> Labels: blocks-1.12.5, blocks-1.13.5, blocks-1.14.0
>
> This fails the most on Windows, but also on Linux. It seems to happen much
> more on 1.12 and 1.13, but also seen on 1.14. However not seen on
> develop...so maybe there is some fix already that just needs to be
> backported? If so please close this as a dupe.
> {noformat}
> org.apache.geode.experimental.driver.SSLTest >
> driverCannotConnectIfProtocolsMismatch FAILED
> java.lang.AssertionError:
> Expected: an instance of javax.net.ssl.SSLException
> but: is a
> java.net.SocketException
> Stacktrace was: java.net.SocketException: Connection reset
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:186)
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:140)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.read(SSLSocketInputRecord.java:478)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.readHeader(SSLSocketInputRecord.java:472)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.decode(SSLSocketInputRecord.java:160)
> at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:111)
> at
> java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1426)
> at
> java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1336)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:450)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:421)
> at
> org.apache.geode.experimental.driver.SocketFactory.connect(SocketFactory.java:146)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.createSocket(ProtobufChannel.java:232)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.findAServer(ProtobufChannel.java:116)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.connectToAServer(ProtobufChannel.java:66)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.(ProtobufChannel.java:49)
> at
> org.apache.geode.experimental.driver.ProtobufDriver.(ProtobufDriver.java:60)
> at
> org.apache.geode.experimental.driver.DriverFactory.create(DriverFactory.java:154)
> at
> org.apache.geode.experimental.driver.SSLTest.driverCannotConnectIfProtocolsMismatch(SSLTest.java:190)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9527) SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
[
https://issues.apache.org/jira/browse/GEODE-9527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401915#comment-17401915
]
Geode Integration commented on GEODE-9527:
--
Seen on support/1.14 in [integration-test-openjdk11
#38|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/integration-test-openjdk11/builds/38]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0840/test-results/integrationTest/1629141905/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0840/test-artifacts/1629141905/integrationtestfiles-openjdk11-1.14.0-build.0840.tgz].
> SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
> ---
>
> Key: GEODE-9527
> URL: https://issues.apache.org/jira/browse/GEODE-9527
> Project: Geode
> Issue Type: Bug
> Components: membership
>Affects Versions: 1.12.4, 1.13.4, 1.14.0
>Reporter: Owen Nichols
>Priority: Major
> Labels: blocks-1.12.5, blocks-1.13.5, blocks-1.14.0
>
> This fails the most on Windows, but also on Linux. It seems to happen much
> more on 1.12 and 1.13, but also seen on 1.14. However not seen on
> develop...so maybe there is some fix already that just needs to be
> backported? If so please close this as a dupe.
> {noformat}
> org.apache.geode.experimental.driver.SSLTest >
> driverCannotConnectIfProtocolsMismatch FAILED
> java.lang.AssertionError:
> Expected: an instance of javax.net.ssl.SSLException
> but: is a
> java.net.SocketException
> Stacktrace was: java.net.SocketException: Connection reset
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:186)
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:140)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.read(SSLSocketInputRecord.java:478)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.readHeader(SSLSocketInputRecord.java:472)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.decode(SSLSocketInputRecord.java:160)
> at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:111)
> at
> java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1426)
> at
> java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1336)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:450)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:421)
> at
> org.apache.geode.experimental.driver.SocketFactory.connect(SocketFactory.java:146)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.createSocket(ProtobufChannel.java:232)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.findAServer(ProtobufChannel.java:116)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.connectToAServer(ProtobufChannel.java:66)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.(ProtobufChannel.java:49)
> at
> org.apache.geode.experimental.driver.ProtobufDriver.(ProtobufDriver.java:60)
> at
> org.apache.geode.experimental.driver.DriverFactory.create(DriverFactory.java:154)
> at
> org.apache.geode.experimental.driver.SSLTest.driverCannotConnectIfProtocolsMismatch(SSLTest.java:190)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9527) SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
[
https://issues.apache.org/jira/browse/GEODE-9527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401912#comment-17401912
]
Geode Integration commented on GEODE-9527:
--
Seen on support/1.12 in [windows-integration-test-openjdk11
#30|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/windows-integration-test-openjdk11/builds/30]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0270/test-results/integrationTest/1629057977/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0270/test-artifacts/1629057977/windows-integrationtestfiles-openjdk11-1.12.5-build.0270.tgz].
> SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
> ---
>
> Key: GEODE-9527
> URL: https://issues.apache.org/jira/browse/GEODE-9527
> Project: Geode
> Issue Type: Bug
> Components: membership
>Affects Versions: 1.12.4, 1.13.4, 1.14.0
>Reporter: Owen Nichols
>Priority: Major
> Labels: blocks-1.12.5, blocks-1.13.5, blocks-1.14.0
>
> This fails the most on Windows, but also on Linux. It seems to happen much
> more on 1.12 and 1.13, but also seen on 1.14. However not seen on
> develop...so maybe there is some fix already that just needs to be
> backported? If so please close this as a dupe.
> {noformat}
> org.apache.geode.experimental.driver.SSLTest >
> driverCannotConnectIfProtocolsMismatch FAILED
> java.lang.AssertionError:
> Expected: an instance of javax.net.ssl.SSLException
> but: is a
> java.net.SocketException
> Stacktrace was: java.net.SocketException: Connection reset
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:186)
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:140)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.read(SSLSocketInputRecord.java:478)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.readHeader(SSLSocketInputRecord.java:472)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.decode(SSLSocketInputRecord.java:160)
> at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:111)
> at
> java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1426)
> at
> java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1336)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:450)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:421)
> at
> org.apache.geode.experimental.driver.SocketFactory.connect(SocketFactory.java:146)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.createSocket(ProtobufChannel.java:232)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.findAServer(ProtobufChannel.java:116)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.connectToAServer(ProtobufChannel.java:66)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.(ProtobufChannel.java:49)
> at
> org.apache.geode.experimental.driver.ProtobufDriver.(ProtobufDriver.java:60)
> at
> org.apache.geode.experimental.driver.DriverFactory.create(DriverFactory.java:154)
> at
> org.apache.geode.experimental.driver.SSLTest.driverCannotConnectIfProtocolsMismatch(SSLTest.java:190)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9527) SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
[
https://issues.apache.org/jira/browse/GEODE-9527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401908#comment-17401908
]
Geode Integration commented on GEODE-9527:
--
Seen on support/1.12 in [windows-integration-test-openjdk11
#25|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/windows-integration-test-openjdk11/builds/25]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0270/test-results/integrationTest/1628885743/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0270/test-artifacts/1628885743/windows-integrationtestfiles-openjdk11-1.12.5-build.0270.tgz].
> SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
> ---
>
> Key: GEODE-9527
> URL: https://issues.apache.org/jira/browse/GEODE-9527
> Project: Geode
> Issue Type: Bug
> Components: membership
>Affects Versions: 1.12.4, 1.13.4, 1.14.0
>Reporter: Owen Nichols
>Priority: Major
> Labels: blocks-1.12.5, blocks-1.13.5, blocks-1.14.0
>
> This fails the most on Windows, but also on Linux. It seems to happen much
> more on 1.12 and 1.13, but also seen on 1.14. However not seen on
> develop...so maybe there is some fix already that just needs to be
> backported? If so please close this as a dupe.
> {noformat}
> org.apache.geode.experimental.driver.SSLTest >
> driverCannotConnectIfProtocolsMismatch FAILED
> java.lang.AssertionError:
> Expected: an instance of javax.net.ssl.SSLException
> but: is a
> java.net.SocketException
> Stacktrace was: java.net.SocketException: Connection reset
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:186)
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:140)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.read(SSLSocketInputRecord.java:478)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.readHeader(SSLSocketInputRecord.java:472)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.decode(SSLSocketInputRecord.java:160)
> at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:111)
> at
> java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1426)
> at
> java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1336)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:450)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:421)
> at
> org.apache.geode.experimental.driver.SocketFactory.connect(SocketFactory.java:146)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.createSocket(ProtobufChannel.java:232)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.findAServer(ProtobufChannel.java:116)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.connectToAServer(ProtobufChannel.java:66)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.(ProtobufChannel.java:49)
> at
> org.apache.geode.experimental.driver.ProtobufDriver.(ProtobufDriver.java:60)
> at
> org.apache.geode.experimental.driver.DriverFactory.create(DriverFactory.java:154)
> at
> org.apache.geode.experimental.driver.SSLTest.driverCannotConnectIfProtocolsMismatch(SSLTest.java:190)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9527) SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
[
https://issues.apache.org/jira/browse/GEODE-9527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401910#comment-17401910
]
Geode Integration commented on GEODE-9527:
--
Seen on support/1.12 in [windows-integration-test-openjdk11
#27|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/windows-integration-test-openjdk11/builds/27]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0270/test-results/integrationTest/1628913725/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0270/test-artifacts/1628913725/windows-integrationtestfiles-openjdk11-1.12.5-build.0270.tgz].
> SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
> ---
>
> Key: GEODE-9527
> URL: https://issues.apache.org/jira/browse/GEODE-9527
> Project: Geode
> Issue Type: Bug
> Components: membership
>Affects Versions: 1.12.4, 1.13.4, 1.14.0
>Reporter: Owen Nichols
>Priority: Major
> Labels: blocks-1.12.5, blocks-1.13.5, blocks-1.14.0
>
> This fails the most on Windows, but also on Linux. It seems to happen much
> more on 1.12 and 1.13, but also seen on 1.14. However not seen on
> develop...so maybe there is some fix already that just needs to be
> backported? If so please close this as a dupe.
> {noformat}
> org.apache.geode.experimental.driver.SSLTest >
> driverCannotConnectIfProtocolsMismatch FAILED
> java.lang.AssertionError:
> Expected: an instance of javax.net.ssl.SSLException
> but: is a
> java.net.SocketException
> Stacktrace was: java.net.SocketException: Connection reset
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:186)
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:140)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.read(SSLSocketInputRecord.java:478)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.readHeader(SSLSocketInputRecord.java:472)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.decode(SSLSocketInputRecord.java:160)
> at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:111)
> at
> java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1426)
> at
> java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1336)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:450)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:421)
> at
> org.apache.geode.experimental.driver.SocketFactory.connect(SocketFactory.java:146)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.createSocket(ProtobufChannel.java:232)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.findAServer(ProtobufChannel.java:116)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.connectToAServer(ProtobufChannel.java:66)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.(ProtobufChannel.java:49)
> at
> org.apache.geode.experimental.driver.ProtobufDriver.(ProtobufDriver.java:60)
> at
> org.apache.geode.experimental.driver.DriverFactory.create(DriverFactory.java:154)
> at
> org.apache.geode.experimental.driver.SSLTest.driverCannotConnectIfProtocolsMismatch(SSLTest.java:190)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9527) SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
[
https://issues.apache.org/jira/browse/GEODE-9527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401909#comment-17401909
]
Geode Integration commented on GEODE-9527:
--
Seen on support/1.12 in [windows-integration-test-openjdk11
#26|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/windows-integration-test-openjdk11/builds/26]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0270/test-results/integrationTest/1628902394/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0270/test-artifacts/1628902394/windows-integrationtestfiles-openjdk11-1.12.5-build.0270.tgz].
> SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
> ---
>
> Key: GEODE-9527
> URL: https://issues.apache.org/jira/browse/GEODE-9527
> Project: Geode
> Issue Type: Bug
> Components: membership
>Affects Versions: 1.12.4, 1.13.4, 1.14.0
>Reporter: Owen Nichols
>Priority: Major
> Labels: blocks-1.12.5, blocks-1.13.5, blocks-1.14.0
>
> This fails the most on Windows, but also on Linux. It seems to happen much
> more on 1.12 and 1.13, but also seen on 1.14. However not seen on
> develop...so maybe there is some fix already that just needs to be
> backported? If so please close this as a dupe.
> {noformat}
> org.apache.geode.experimental.driver.SSLTest >
> driverCannotConnectIfProtocolsMismatch FAILED
> java.lang.AssertionError:
> Expected: an instance of javax.net.ssl.SSLException
> but: is a
> java.net.SocketException
> Stacktrace was: java.net.SocketException: Connection reset
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:186)
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:140)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.read(SSLSocketInputRecord.java:478)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.readHeader(SSLSocketInputRecord.java:472)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.decode(SSLSocketInputRecord.java:160)
> at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:111)
> at
> java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1426)
> at
> java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1336)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:450)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:421)
> at
> org.apache.geode.experimental.driver.SocketFactory.connect(SocketFactory.java:146)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.createSocket(ProtobufChannel.java:232)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.findAServer(ProtobufChannel.java:116)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.connectToAServer(ProtobufChannel.java:66)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.(ProtobufChannel.java:49)
> at
> org.apache.geode.experimental.driver.ProtobufDriver.(ProtobufDriver.java:60)
> at
> org.apache.geode.experimental.driver.DriverFactory.create(DriverFactory.java:154)
> at
> org.apache.geode.experimental.driver.SSLTest.driverCannotConnectIfProtocolsMismatch(SSLTest.java:190)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9527) SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
[
https://issues.apache.org/jira/browse/GEODE-9527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401913#comment-17401913
]
Geode Integration commented on GEODE-9527:
--
Seen on support/1.12 in [windows-integration-test-openjdk11
#31|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/windows-integration-test-openjdk11/builds/31]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0270/test-results/integrationTest/1629070602/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0270/test-artifacts/1629070602/windows-integrationtestfiles-openjdk11-1.12.5-build.0270.tgz].
> SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
> ---
>
> Key: GEODE-9527
> URL: https://issues.apache.org/jira/browse/GEODE-9527
> Project: Geode
> Issue Type: Bug
> Components: membership
>Affects Versions: 1.12.4, 1.13.4, 1.14.0
>Reporter: Owen Nichols
>Priority: Major
> Labels: blocks-1.12.5, blocks-1.13.5, blocks-1.14.0
>
> This fails the most on Windows, but also on Linux. It seems to happen much
> more on 1.12 and 1.13, but also seen on 1.14. However not seen on
> develop...so maybe there is some fix already that just needs to be
> backported? If so please close this as a dupe.
> {noformat}
> org.apache.geode.experimental.driver.SSLTest >
> driverCannotConnectIfProtocolsMismatch FAILED
> java.lang.AssertionError:
> Expected: an instance of javax.net.ssl.SSLException
> but: is a
> java.net.SocketException
> Stacktrace was: java.net.SocketException: Connection reset
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:186)
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:140)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.read(SSLSocketInputRecord.java:478)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.readHeader(SSLSocketInputRecord.java:472)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.decode(SSLSocketInputRecord.java:160)
> at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:111)
> at
> java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1426)
> at
> java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1336)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:450)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:421)
> at
> org.apache.geode.experimental.driver.SocketFactory.connect(SocketFactory.java:146)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.createSocket(ProtobufChannel.java:232)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.findAServer(ProtobufChannel.java:116)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.connectToAServer(ProtobufChannel.java:66)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.(ProtobufChannel.java:49)
> at
> org.apache.geode.experimental.driver.ProtobufDriver.(ProtobufDriver.java:60)
> at
> org.apache.geode.experimental.driver.DriverFactory.create(DriverFactory.java:154)
> at
> org.apache.geode.experimental.driver.SSLTest.driverCannotConnectIfProtocolsMismatch(SSLTest.java:190)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9527) SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
[
https://issues.apache.org/jira/browse/GEODE-9527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401905#comment-17401905
]
Geode Integration commented on GEODE-9527:
--
Seen on support/1.12 in [integration-test-openjdk11
#28|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/integration-test-openjdk11/builds/28]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0269/test-results/integrationTest/1628814108/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0269/test-artifacts/1628814108/integrationtestfiles-openjdk11-1.12.5-build.0269.tgz].
> SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
> ---
>
> Key: GEODE-9527
> URL: https://issues.apache.org/jira/browse/GEODE-9527
> Project: Geode
> Issue Type: Bug
> Components: membership
>Affects Versions: 1.12.4, 1.13.4, 1.14.0
>Reporter: Owen Nichols
>Priority: Major
> Labels: blocks-1.12.5, blocks-1.13.5, blocks-1.14.0
>
> This fails the most on Windows, but also on Linux. It seems to happen much
> more on 1.12 and 1.13, but also seen on 1.14. However not seen on
> develop...so maybe there is some fix already that just needs to be
> backported? If so please close this as a dupe.
> {noformat}
> org.apache.geode.experimental.driver.SSLTest >
> driverCannotConnectIfProtocolsMismatch FAILED
> java.lang.AssertionError:
> Expected: an instance of javax.net.ssl.SSLException
> but: is a
> java.net.SocketException
> Stacktrace was: java.net.SocketException: Connection reset
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:186)
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:140)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.read(SSLSocketInputRecord.java:478)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.readHeader(SSLSocketInputRecord.java:472)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.decode(SSLSocketInputRecord.java:160)
> at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:111)
> at
> java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1426)
> at
> java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1336)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:450)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:421)
> at
> org.apache.geode.experimental.driver.SocketFactory.connect(SocketFactory.java:146)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.createSocket(ProtobufChannel.java:232)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.findAServer(ProtobufChannel.java:116)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.connectToAServer(ProtobufChannel.java:66)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.(ProtobufChannel.java:49)
> at
> org.apache.geode.experimental.driver.ProtobufDriver.(ProtobufDriver.java:60)
> at
> org.apache.geode.experimental.driver.DriverFactory.create(DriverFactory.java:154)
> at
> org.apache.geode.experimental.driver.SSLTest.driverCannotConnectIfProtocolsMismatch(SSLTest.java:190)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9527) SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
[
https://issues.apache.org/jira/browse/GEODE-9527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401902#comment-17401902
]
Geode Integration commented on GEODE-9527:
--
Seen on support/1.12 in [integration-test-openjdk11
#27|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/integration-test-openjdk11/builds/27]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0269/test-results/integrationTest/1628805706/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0269/test-artifacts/1628805706/integrationtestfiles-openjdk11-1.12.5-build.0269.tgz].
> SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
> ---
>
> Key: GEODE-9527
> URL: https://issues.apache.org/jira/browse/GEODE-9527
> Project: Geode
> Issue Type: Bug
> Components: membership
>Affects Versions: 1.12.4, 1.13.4, 1.14.0
>Reporter: Owen Nichols
>Priority: Major
> Labels: blocks-1.12.5, blocks-1.13.5, blocks-1.14.0
>
> This fails the most on Windows, but also on Linux. It seems to happen much
> more on 1.12 and 1.13, but also seen on 1.14. However not seen on
> develop...so maybe there is some fix already that just needs to be
> backported? If so please close this as a dupe.
> {noformat}
> org.apache.geode.experimental.driver.SSLTest >
> driverCannotConnectIfProtocolsMismatch FAILED
> java.lang.AssertionError:
> Expected: an instance of javax.net.ssl.SSLException
> but: is a
> java.net.SocketException
> Stacktrace was: java.net.SocketException: Connection reset
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:186)
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:140)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.read(SSLSocketInputRecord.java:478)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.readHeader(SSLSocketInputRecord.java:472)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.decode(SSLSocketInputRecord.java:160)
> at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:111)
> at
> java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1426)
> at
> java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1336)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:450)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:421)
> at
> org.apache.geode.experimental.driver.SocketFactory.connect(SocketFactory.java:146)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.createSocket(ProtobufChannel.java:232)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.findAServer(ProtobufChannel.java:116)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.connectToAServer(ProtobufChannel.java:66)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.(ProtobufChannel.java:49)
> at
> org.apache.geode.experimental.driver.ProtobufDriver.(ProtobufDriver.java:60)
> at
> org.apache.geode.experimental.driver.DriverFactory.create(DriverFactory.java:154)
> at
> org.apache.geode.experimental.driver.SSLTest.driverCannotConnectIfProtocolsMismatch(SSLTest.java:190)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9527) SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
[
https://issues.apache.org/jira/browse/GEODE-9527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401911#comment-17401911
]
Geode Integration commented on GEODE-9527:
--
Seen on support/1.12 in [windows-integration-test-openjdk11
#29|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/windows-integration-test-openjdk11/builds/29]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0270/test-results/integrationTest/1629019681/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0270/test-artifacts/1629019681/windows-integrationtestfiles-openjdk11-1.12.5-build.0270.tgz].
> SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
> ---
>
> Key: GEODE-9527
> URL: https://issues.apache.org/jira/browse/GEODE-9527
> Project: Geode
> Issue Type: Bug
> Components: membership
>Affects Versions: 1.12.4, 1.13.4, 1.14.0
>Reporter: Owen Nichols
>Priority: Major
> Labels: blocks-1.12.5, blocks-1.13.5, blocks-1.14.0
>
> This fails the most on Windows, but also on Linux. It seems to happen much
> more on 1.12 and 1.13, but also seen on 1.14. However not seen on
> develop...so maybe there is some fix already that just needs to be
> backported? If so please close this as a dupe.
> {noformat}
> org.apache.geode.experimental.driver.SSLTest >
> driverCannotConnectIfProtocolsMismatch FAILED
> java.lang.AssertionError:
> Expected: an instance of javax.net.ssl.SSLException
> but: is a
> java.net.SocketException
> Stacktrace was: java.net.SocketException: Connection reset
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:186)
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:140)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.read(SSLSocketInputRecord.java:478)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.readHeader(SSLSocketInputRecord.java:472)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.decode(SSLSocketInputRecord.java:160)
> at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:111)
> at
> java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1426)
> at
> java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1336)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:450)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:421)
> at
> org.apache.geode.experimental.driver.SocketFactory.connect(SocketFactory.java:146)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.createSocket(ProtobufChannel.java:232)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.findAServer(ProtobufChannel.java:116)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.connectToAServer(ProtobufChannel.java:66)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.(ProtobufChannel.java:49)
> at
> org.apache.geode.experimental.driver.ProtobufDriver.(ProtobufDriver.java:60)
> at
> org.apache.geode.experimental.driver.DriverFactory.create(DriverFactory.java:154)
> at
> org.apache.geode.experimental.driver.SSLTest.driverCannotConnectIfProtocolsMismatch(SSLTest.java:190)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9527) SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
[
https://issues.apache.org/jira/browse/GEODE-9527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401906#comment-17401906
]
Geode Integration commented on GEODE-9527:
--
Seen on support/1.12 in [integration-test-openjdk11
#32|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/integration-test-openjdk11/builds/32]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0270/test-results/integrationTest/1628844252/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0270/test-artifacts/1628844252/integrationtestfiles-openjdk11-1.12.5-build.0270.tgz].
> SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
> ---
>
> Key: GEODE-9527
> URL: https://issues.apache.org/jira/browse/GEODE-9527
> Project: Geode
> Issue Type: Bug
> Components: membership
>Affects Versions: 1.12.4, 1.13.4, 1.14.0
>Reporter: Owen Nichols
>Priority: Major
> Labels: blocks-1.12.5, blocks-1.13.5, blocks-1.14.0
>
> This fails the most on Windows, but also on Linux. It seems to happen much
> more on 1.12 and 1.13, but also seen on 1.14. However not seen on
> develop...so maybe there is some fix already that just needs to be
> backported? If so please close this as a dupe.
> {noformat}
> org.apache.geode.experimental.driver.SSLTest >
> driverCannotConnectIfProtocolsMismatch FAILED
> java.lang.AssertionError:
> Expected: an instance of javax.net.ssl.SSLException
> but: is a
> java.net.SocketException
> Stacktrace was: java.net.SocketException: Connection reset
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:186)
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:140)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.read(SSLSocketInputRecord.java:478)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.readHeader(SSLSocketInputRecord.java:472)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.decode(SSLSocketInputRecord.java:160)
> at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:111)
> at
> java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1426)
> at
> java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1336)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:450)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:421)
> at
> org.apache.geode.experimental.driver.SocketFactory.connect(SocketFactory.java:146)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.createSocket(ProtobufChannel.java:232)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.findAServer(ProtobufChannel.java:116)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.connectToAServer(ProtobufChannel.java:66)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.(ProtobufChannel.java:49)
> at
> org.apache.geode.experimental.driver.ProtobufDriver.(ProtobufDriver.java:60)
> at
> org.apache.geode.experimental.driver.DriverFactory.create(DriverFactory.java:154)
> at
> org.apache.geode.experimental.driver.SSLTest.driverCannotConnectIfProtocolsMismatch(SSLTest.java:190)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9527) SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
[
https://issues.apache.org/jira/browse/GEODE-9527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401914#comment-17401914
]
Geode Integration commented on GEODE-9527:
--
Seen on support/1.12 in [windows-integration-test-openjdk11
#32|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/windows-integration-test-openjdk11/builds/32]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0270/test-results/integrationTest/1629100713/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0270/test-artifacts/1629100713/windows-integrationtestfiles-openjdk11-1.12.5-build.0270.tgz].
> SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
> ---
>
> Key: GEODE-9527
> URL: https://issues.apache.org/jira/browse/GEODE-9527
> Project: Geode
> Issue Type: Bug
> Components: membership
>Affects Versions: 1.12.4, 1.13.4, 1.14.0
>Reporter: Owen Nichols
>Priority: Major
> Labels: blocks-1.12.5, blocks-1.13.5, blocks-1.14.0
>
> This fails the most on Windows, but also on Linux. It seems to happen much
> more on 1.12 and 1.13, but also seen on 1.14. However not seen on
> develop...so maybe there is some fix already that just needs to be
> backported? If so please close this as a dupe.
> {noformat}
> org.apache.geode.experimental.driver.SSLTest >
> driverCannotConnectIfProtocolsMismatch FAILED
> java.lang.AssertionError:
> Expected: an instance of javax.net.ssl.SSLException
> but: is a
> java.net.SocketException
> Stacktrace was: java.net.SocketException: Connection reset
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:186)
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:140)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.read(SSLSocketInputRecord.java:478)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.readHeader(SSLSocketInputRecord.java:472)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.decode(SSLSocketInputRecord.java:160)
> at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:111)
> at
> java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1426)
> at
> java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1336)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:450)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:421)
> at
> org.apache.geode.experimental.driver.SocketFactory.connect(SocketFactory.java:146)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.createSocket(ProtobufChannel.java:232)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.findAServer(ProtobufChannel.java:116)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.connectToAServer(ProtobufChannel.java:66)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.(ProtobufChannel.java:49)
> at
> org.apache.geode.experimental.driver.ProtobufDriver.(ProtobufDriver.java:60)
> at
> org.apache.geode.experimental.driver.DriverFactory.create(DriverFactory.java:154)
> at
> org.apache.geode.experimental.driver.SSLTest.driverCannotConnectIfProtocolsMismatch(SSLTest.java:190)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9527) SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
[
https://issues.apache.org/jira/browse/GEODE-9527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401916#comment-17401916
]
Geode Integration commented on GEODE-9527:
--
Seen on support/1.12 in [windows-integration-test-openjdk11
#33|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/windows-integration-test-openjdk11/builds/33]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0270/test-results/integrationTest/1629144476/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0270/test-artifacts/1629144476/windows-integrationtestfiles-openjdk11-1.12.5-build.0270.tgz].
> SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
> ---
>
> Key: GEODE-9527
> URL: https://issues.apache.org/jira/browse/GEODE-9527
> Project: Geode
> Issue Type: Bug
> Components: membership
>Affects Versions: 1.12.4, 1.13.4, 1.14.0
>Reporter: Owen Nichols
>Priority: Major
> Labels: blocks-1.12.5, blocks-1.13.5, blocks-1.14.0
>
> This fails the most on Windows, but also on Linux. It seems to happen much
> more on 1.12 and 1.13, but also seen on 1.14. However not seen on
> develop...so maybe there is some fix already that just needs to be
> backported? If so please close this as a dupe.
> {noformat}
> org.apache.geode.experimental.driver.SSLTest >
> driverCannotConnectIfProtocolsMismatch FAILED
> java.lang.AssertionError:
> Expected: an instance of javax.net.ssl.SSLException
> but: is a
> java.net.SocketException
> Stacktrace was: java.net.SocketException: Connection reset
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:186)
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:140)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.read(SSLSocketInputRecord.java:478)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.readHeader(SSLSocketInputRecord.java:472)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.decode(SSLSocketInputRecord.java:160)
> at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:111)
> at
> java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1426)
> at
> java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1336)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:450)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:421)
> at
> org.apache.geode.experimental.driver.SocketFactory.connect(SocketFactory.java:146)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.createSocket(ProtobufChannel.java:232)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.findAServer(ProtobufChannel.java:116)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.connectToAServer(ProtobufChannel.java:66)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.(ProtobufChannel.java:49)
> at
> org.apache.geode.experimental.driver.ProtobufDriver.(ProtobufDriver.java:60)
> at
> org.apache.geode.experimental.driver.DriverFactory.create(DriverFactory.java:154)
> at
> org.apache.geode.experimental.driver.SSLTest.driverCannotConnectIfProtocolsMismatch(SSLTest.java:190)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9527) SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
[
https://issues.apache.org/jira/browse/GEODE-9527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401904#comment-17401904
]
Geode Integration commented on GEODE-9527:
--
Seen on support/1.14 in [integration-test-openjdk11
#36|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/integration-test-openjdk11/builds/36]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0838/test-results/integrationTest/1628806637/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0838/test-artifacts/1628806637/integrationtestfiles-openjdk11-1.14.0-build.0838.tgz].
> SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
> ---
>
> Key: GEODE-9527
> URL: https://issues.apache.org/jira/browse/GEODE-9527
> Project: Geode
> Issue Type: Bug
> Components: membership
>Affects Versions: 1.12.4, 1.13.4, 1.14.0
>Reporter: Owen Nichols
>Priority: Major
> Labels: blocks-1.12.5, blocks-1.13.5, blocks-1.14.0
>
> This fails the most on Windows, but also on Linux. It seems to happen much
> more on 1.12 and 1.13, but also seen on 1.14. However not seen on
> develop...so maybe there is some fix already that just needs to be
> backported? If so please close this as a dupe.
> {noformat}
> org.apache.geode.experimental.driver.SSLTest >
> driverCannotConnectIfProtocolsMismatch FAILED
> java.lang.AssertionError:
> Expected: an instance of javax.net.ssl.SSLException
> but: is a
> java.net.SocketException
> Stacktrace was: java.net.SocketException: Connection reset
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:186)
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:140)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.read(SSLSocketInputRecord.java:478)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.readHeader(SSLSocketInputRecord.java:472)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.decode(SSLSocketInputRecord.java:160)
> at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:111)
> at
> java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1426)
> at
> java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1336)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:450)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:421)
> at
> org.apache.geode.experimental.driver.SocketFactory.connect(SocketFactory.java:146)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.createSocket(ProtobufChannel.java:232)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.findAServer(ProtobufChannel.java:116)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.connectToAServer(ProtobufChannel.java:66)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.(ProtobufChannel.java:49)
> at
> org.apache.geode.experimental.driver.ProtobufDriver.(ProtobufDriver.java:60)
> at
> org.apache.geode.experimental.driver.DriverFactory.create(DriverFactory.java:154)
> at
> org.apache.geode.experimental.driver.SSLTest.driverCannotConnectIfProtocolsMismatch(SSLTest.java:190)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9527) SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
[
https://issues.apache.org/jira/browse/GEODE-9527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401922#comment-17401922
]
Geode Integration commented on GEODE-9527:
--
Seen on support/1.14 in [windows-integration-test-openjdk11
#35|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/windows-integration-test-openjdk11/builds/35]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0840/test-results/integrationTest/1629164971/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0840/test-artifacts/1629164971/windows-integrationtestfiles-openjdk11-1.14.0-build.0840.tgz].
> SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
> ---
>
> Key: GEODE-9527
> URL: https://issues.apache.org/jira/browse/GEODE-9527
> Project: Geode
> Issue Type: Bug
> Components: membership
>Affects Versions: 1.12.4, 1.13.4, 1.14.0
>Reporter: Owen Nichols
>Priority: Major
> Labels: blocks-1.12.5, blocks-1.13.5, blocks-1.14.0
>
> This fails the most on Windows, but also on Linux. It seems to happen much
> more on 1.12 and 1.13, but also seen on 1.14. However not seen on
> develop...so maybe there is some fix already that just needs to be
> backported? If so please close this as a dupe.
> {noformat}
> org.apache.geode.experimental.driver.SSLTest >
> driverCannotConnectIfProtocolsMismatch FAILED
> java.lang.AssertionError:
> Expected: an instance of javax.net.ssl.SSLException
> but: is a
> java.net.SocketException
> Stacktrace was: java.net.SocketException: Connection reset
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:186)
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:140)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.read(SSLSocketInputRecord.java:478)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.readHeader(SSLSocketInputRecord.java:472)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.decode(SSLSocketInputRecord.java:160)
> at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:111)
> at
> java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1426)
> at
> java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1336)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:450)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:421)
> at
> org.apache.geode.experimental.driver.SocketFactory.connect(SocketFactory.java:146)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.createSocket(ProtobufChannel.java:232)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.findAServer(ProtobufChannel.java:116)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.connectToAServer(ProtobufChannel.java:66)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.(ProtobufChannel.java:49)
> at
> org.apache.geode.experimental.driver.ProtobufDriver.(ProtobufDriver.java:60)
> at
> org.apache.geode.experimental.driver.DriverFactory.create(DriverFactory.java:154)
> at
> org.apache.geode.experimental.driver.SSLTest.driverCannotConnectIfProtocolsMismatch(SSLTest.java:190)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9527) SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
[
https://issues.apache.org/jira/browse/GEODE-9527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401919#comment-17401919
]
Geode Integration commented on GEODE-9527:
--
Seen on support/1.12 in [windows-integration-test-openjdk11
#34|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/windows-integration-test-openjdk11/builds/34]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0270/test-results/integrationTest/1629153622/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0270/test-artifacts/1629153622/windows-integrationtestfiles-openjdk11-1.12.5-build.0270.tgz].
> SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
> ---
>
> Key: GEODE-9527
> URL: https://issues.apache.org/jira/browse/GEODE-9527
> Project: Geode
> Issue Type: Bug
> Components: membership
>Affects Versions: 1.12.4, 1.13.4, 1.14.0
>Reporter: Owen Nichols
>Priority: Major
> Labels: blocks-1.12.5, blocks-1.13.5, blocks-1.14.0
>
> This fails the most on Windows, but also on Linux. It seems to happen much
> more on 1.12 and 1.13, but also seen on 1.14. However not seen on
> develop...so maybe there is some fix already that just needs to be
> backported? If so please close this as a dupe.
> {noformat}
> org.apache.geode.experimental.driver.SSLTest >
> driverCannotConnectIfProtocolsMismatch FAILED
> java.lang.AssertionError:
> Expected: an instance of javax.net.ssl.SSLException
> but: is a
> java.net.SocketException
> Stacktrace was: java.net.SocketException: Connection reset
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:186)
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:140)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.read(SSLSocketInputRecord.java:478)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.readHeader(SSLSocketInputRecord.java:472)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.decode(SSLSocketInputRecord.java:160)
> at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:111)
> at
> java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1426)
> at
> java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1336)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:450)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:421)
> at
> org.apache.geode.experimental.driver.SocketFactory.connect(SocketFactory.java:146)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.createSocket(ProtobufChannel.java:232)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.findAServer(ProtobufChannel.java:116)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.connectToAServer(ProtobufChannel.java:66)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.(ProtobufChannel.java:49)
> at
> org.apache.geode.experimental.driver.ProtobufDriver.(ProtobufDriver.java:60)
> at
> org.apache.geode.experimental.driver.DriverFactory.create(DriverFactory.java:154)
> at
> org.apache.geode.experimental.driver.SSLTest.driverCannotConnectIfProtocolsMismatch(SSLTest.java:190)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9527) SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
[
https://issues.apache.org/jira/browse/GEODE-9527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401917#comment-17401917
]
Geode Integration commented on GEODE-9527:
--
Seen on support/1.13 in [integration-test-openjdk11
#40|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-main/jobs/integration-test-openjdk11/builds/40]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.5-build.0577/test-results/integrationTest/1629148328/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.5-build.0577/test-artifacts/1629148328/integrationtestfiles-openjdk11-1.13.5-build.0577.tgz].
> SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
> ---
>
> Key: GEODE-9527
> URL: https://issues.apache.org/jira/browse/GEODE-9527
> Project: Geode
> Issue Type: Bug
> Components: membership
>Affects Versions: 1.12.4, 1.13.4, 1.14.0
>Reporter: Owen Nichols
>Priority: Major
> Labels: blocks-1.12.5, blocks-1.13.5, blocks-1.14.0
>
> This fails the most on Windows, but also on Linux. It seems to happen much
> more on 1.12 and 1.13, but also seen on 1.14. However not seen on
> develop...so maybe there is some fix already that just needs to be
> backported? If so please close this as a dupe.
> {noformat}
> org.apache.geode.experimental.driver.SSLTest >
> driverCannotConnectIfProtocolsMismatch FAILED
> java.lang.AssertionError:
> Expected: an instance of javax.net.ssl.SSLException
> but: is a
> java.net.SocketException
> Stacktrace was: java.net.SocketException: Connection reset
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:186)
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:140)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.read(SSLSocketInputRecord.java:478)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.readHeader(SSLSocketInputRecord.java:472)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.decode(SSLSocketInputRecord.java:160)
> at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:111)
> at
> java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1426)
> at
> java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1336)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:450)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:421)
> at
> org.apache.geode.experimental.driver.SocketFactory.connect(SocketFactory.java:146)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.createSocket(ProtobufChannel.java:232)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.findAServer(ProtobufChannel.java:116)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.connectToAServer(ProtobufChannel.java:66)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.(ProtobufChannel.java:49)
> at
> org.apache.geode.experimental.driver.ProtobufDriver.(ProtobufDriver.java:60)
> at
> org.apache.geode.experimental.driver.DriverFactory.create(DriverFactory.java:154)
> at
> org.apache.geode.experimental.driver.SSLTest.driverCannotConnectIfProtocolsMismatch(SSLTest.java:190)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9527) SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
[
https://issues.apache.org/jira/browse/GEODE-9527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401923#comment-17401923
]
Geode Integration commented on GEODE-9527:
--
Seen on support/1.13 in [windows-integration-test-openjdk11
#38|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-main/jobs/windows-integration-test-openjdk11/builds/38]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.5-build.0577/test-results/integrationTest/1629167457/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.5-build.0577/test-artifacts/1629167457/windows-integrationtestfiles-openjdk11-1.13.5-build.0577.tgz].
> SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
> ---
>
> Key: GEODE-9527
> URL: https://issues.apache.org/jira/browse/GEODE-9527
> Project: Geode
> Issue Type: Bug
> Components: membership
>Affects Versions: 1.12.4, 1.13.4, 1.14.0
>Reporter: Owen Nichols
>Priority: Major
> Labels: blocks-1.12.5, blocks-1.13.5, blocks-1.14.0
>
> This fails the most on Windows, but also on Linux. It seems to happen much
> more on 1.12 and 1.13, but also seen on 1.14. However not seen on
> develop...so maybe there is some fix already that just needs to be
> backported? If so please close this as a dupe.
> {noformat}
> org.apache.geode.experimental.driver.SSLTest >
> driverCannotConnectIfProtocolsMismatch FAILED
> java.lang.AssertionError:
> Expected: an instance of javax.net.ssl.SSLException
> but: is a
> java.net.SocketException
> Stacktrace was: java.net.SocketException: Connection reset
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:186)
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:140)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.read(SSLSocketInputRecord.java:478)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.readHeader(SSLSocketInputRecord.java:472)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.decode(SSLSocketInputRecord.java:160)
> at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:111)
> at
> java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1426)
> at
> java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1336)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:450)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:421)
> at
> org.apache.geode.experimental.driver.SocketFactory.connect(SocketFactory.java:146)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.createSocket(ProtobufChannel.java:232)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.findAServer(ProtobufChannel.java:116)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.connectToAServer(ProtobufChannel.java:66)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.(ProtobufChannel.java:49)
> at
> org.apache.geode.experimental.driver.ProtobufDriver.(ProtobufDriver.java:60)
> at
> org.apache.geode.experimental.driver.DriverFactory.create(DriverFactory.java:154)
> at
> org.apache.geode.experimental.driver.SSLTest.driverCannotConnectIfProtocolsMismatch(SSLTest.java:190)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9527) SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
[
https://issues.apache.org/jira/browse/GEODE-9527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401924#comment-17401924
]
Geode Integration commented on GEODE-9527:
--
Seen on support/1.13 in [integration-test-openjdk11
#47|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-main/jobs/integration-test-openjdk11/builds/47]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.5-build.0578/test-results/integrationTest/1629323521/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.5-build.0578/test-artifacts/1629323521/integrationtestfiles-openjdk11-1.13.5-build.0578.tgz].
> SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
> ---
>
> Key: GEODE-9527
> URL: https://issues.apache.org/jira/browse/GEODE-9527
> Project: Geode
> Issue Type: Bug
> Components: membership
>Affects Versions: 1.12.4, 1.13.4, 1.14.0
>Reporter: Owen Nichols
>Priority: Major
> Labels: blocks-1.12.5, blocks-1.13.5, blocks-1.14.0
>
> This fails the most on Windows, but also on Linux. It seems to happen much
> more on 1.12 and 1.13, but also seen on 1.14. However not seen on
> develop...so maybe there is some fix already that just needs to be
> backported? If so please close this as a dupe.
> {noformat}
> org.apache.geode.experimental.driver.SSLTest >
> driverCannotConnectIfProtocolsMismatch FAILED
> java.lang.AssertionError:
> Expected: an instance of javax.net.ssl.SSLException
> but: is a
> java.net.SocketException
> Stacktrace was: java.net.SocketException: Connection reset
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:186)
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:140)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.read(SSLSocketInputRecord.java:478)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.readHeader(SSLSocketInputRecord.java:472)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.decode(SSLSocketInputRecord.java:160)
> at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:111)
> at
> java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1426)
> at
> java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1336)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:450)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:421)
> at
> org.apache.geode.experimental.driver.SocketFactory.connect(SocketFactory.java:146)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.createSocket(ProtobufChannel.java:232)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.findAServer(ProtobufChannel.java:116)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.connectToAServer(ProtobufChannel.java:66)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.(ProtobufChannel.java:49)
> at
> org.apache.geode.experimental.driver.ProtobufDriver.(ProtobufDriver.java:60)
> at
> org.apache.geode.experimental.driver.DriverFactory.create(DriverFactory.java:154)
> at
> org.apache.geode.experimental.driver.SSLTest.driverCannotConnectIfProtocolsMismatch(SSLTest.java:190)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9527) SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
[
https://issues.apache.org/jira/browse/GEODE-9527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401920#comment-17401920
]
Geode Integration commented on GEODE-9527:
--
Seen on support/1.13 in [windows-integration-test-openjdk11
#37|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-main/jobs/windows-integration-test-openjdk11/builds/37]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.5-build.0577/test-results/integrationTest/1629157325/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.5-build.0577/test-artifacts/1629157325/windows-integrationtestfiles-openjdk11-1.13.5-build.0577.tgz].
> SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
> ---
>
> Key: GEODE-9527
> URL: https://issues.apache.org/jira/browse/GEODE-9527
> Project: Geode
> Issue Type: Bug
> Components: membership
>Affects Versions: 1.12.4, 1.13.4, 1.14.0
>Reporter: Owen Nichols
>Priority: Major
> Labels: blocks-1.12.5, blocks-1.13.5, blocks-1.14.0
>
> This fails the most on Windows, but also on Linux. It seems to happen much
> more on 1.12 and 1.13, but also seen on 1.14. However not seen on
> develop...so maybe there is some fix already that just needs to be
> backported? If so please close this as a dupe.
> {noformat}
> org.apache.geode.experimental.driver.SSLTest >
> driverCannotConnectIfProtocolsMismatch FAILED
> java.lang.AssertionError:
> Expected: an instance of javax.net.ssl.SSLException
> but: is a
> java.net.SocketException
> Stacktrace was: java.net.SocketException: Connection reset
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:186)
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:140)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.read(SSLSocketInputRecord.java:478)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.readHeader(SSLSocketInputRecord.java:472)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.decode(SSLSocketInputRecord.java:160)
> at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:111)
> at
> java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1426)
> at
> java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1336)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:450)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:421)
> at
> org.apache.geode.experimental.driver.SocketFactory.connect(SocketFactory.java:146)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.createSocket(ProtobufChannel.java:232)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.findAServer(ProtobufChannel.java:116)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.connectToAServer(ProtobufChannel.java:66)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.(ProtobufChannel.java:49)
> at
> org.apache.geode.experimental.driver.ProtobufDriver.(ProtobufDriver.java:60)
> at
> org.apache.geode.experimental.driver.DriverFactory.create(DriverFactory.java:154)
> at
> org.apache.geode.experimental.driver.SSLTest.driverCannotConnectIfProtocolsMismatch(SSLTest.java:190)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9527) SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
[
https://issues.apache.org/jira/browse/GEODE-9527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401918#comment-17401918
]
Geode Integration commented on GEODE-9527:
--
Seen on support/1.13 in [windows-integration-test-openjdk11
#36|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-main/jobs/windows-integration-test-openjdk11/builds/36]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.5-build.0577/test-results/integrationTest/1629148870/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.5-build.0577/test-artifacts/1629148870/windows-integrationtestfiles-openjdk11-1.13.5-build.0577.tgz].
> SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
> ---
>
> Key: GEODE-9527
> URL: https://issues.apache.org/jira/browse/GEODE-9527
> Project: Geode
> Issue Type: Bug
> Components: membership
>Affects Versions: 1.12.4, 1.13.4, 1.14.0
>Reporter: Owen Nichols
>Priority: Major
> Labels: blocks-1.12.5, blocks-1.13.5, blocks-1.14.0
>
> This fails the most on Windows, but also on Linux. It seems to happen much
> more on 1.12 and 1.13, but also seen on 1.14. However not seen on
> develop...so maybe there is some fix already that just needs to be
> backported? If so please close this as a dupe.
> {noformat}
> org.apache.geode.experimental.driver.SSLTest >
> driverCannotConnectIfProtocolsMismatch FAILED
> java.lang.AssertionError:
> Expected: an instance of javax.net.ssl.SSLException
> but: is a
> java.net.SocketException
> Stacktrace was: java.net.SocketException: Connection reset
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:186)
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:140)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.read(SSLSocketInputRecord.java:478)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.readHeader(SSLSocketInputRecord.java:472)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.decode(SSLSocketInputRecord.java:160)
> at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:111)
> at
> java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1426)
> at
> java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1336)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:450)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:421)
> at
> org.apache.geode.experimental.driver.SocketFactory.connect(SocketFactory.java:146)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.createSocket(ProtobufChannel.java:232)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.findAServer(ProtobufChannel.java:116)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.connectToAServer(ProtobufChannel.java:66)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.(ProtobufChannel.java:49)
> at
> org.apache.geode.experimental.driver.ProtobufDriver.(ProtobufDriver.java:60)
> at
> org.apache.geode.experimental.driver.DriverFactory.create(DriverFactory.java:154)
> at
> org.apache.geode.experimental.driver.SSLTest.driverCannotConnectIfProtocolsMismatch(SSLTest.java:190)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9527) SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
[
https://issues.apache.org/jira/browse/GEODE-9527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401921#comment-17401921
]
Geode Integration commented on GEODE-9527:
--
Seen on support/1.12 in [windows-integration-test-openjdk11
#35|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/windows-integration-test-openjdk11/builds/35]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0270/test-results/integrationTest/1629161866/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0270/test-artifacts/1629161866/windows-integrationtestfiles-openjdk11-1.12.5-build.0270.tgz].
> SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12
> ---
>
> Key: GEODE-9527
> URL: https://issues.apache.org/jira/browse/GEODE-9527
> Project: Geode
> Issue Type: Bug
> Components: membership
>Affects Versions: 1.12.4, 1.13.4, 1.14.0
>Reporter: Owen Nichols
>Priority: Major
> Labels: blocks-1.12.5, blocks-1.13.5, blocks-1.14.0
>
> This fails the most on Windows, but also on Linux. It seems to happen much
> more on 1.12 and 1.13, but also seen on 1.14. However not seen on
> develop...so maybe there is some fix already that just needs to be
> backported? If so please close this as a dupe.
> {noformat}
> org.apache.geode.experimental.driver.SSLTest >
> driverCannotConnectIfProtocolsMismatch FAILED
> java.lang.AssertionError:
> Expected: an instance of javax.net.ssl.SSLException
> but: is a
> java.net.SocketException
> Stacktrace was: java.net.SocketException: Connection reset
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:186)
> at java.base/java.net.SocketInputStream.read(SocketInputStream.java:140)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.read(SSLSocketInputRecord.java:478)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.readHeader(SSLSocketInputRecord.java:472)
> at
> java.base/sun.security.ssl.SSLSocketInputRecord.decode(SSLSocketInputRecord.java:160)
> at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:111)
> at
> java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1426)
> at
> java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1336)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:450)
> at
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:421)
> at
> org.apache.geode.experimental.driver.SocketFactory.connect(SocketFactory.java:146)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.createSocket(ProtobufChannel.java:232)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.findAServer(ProtobufChannel.java:116)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.connectToAServer(ProtobufChannel.java:66)
> at
> org.apache.geode.experimental.driver.ProtobufChannel.(ProtobufChannel.java:49)
> at
> org.apache.geode.experimental.driver.ProtobufDriver.(ProtobufDriver.java:60)
> at
> org.apache.geode.experimental.driver.DriverFactory.create(DriverFactory.java:154)
> at
> org.apache.geode.experimental.driver.SSLTest.driverCannotConnectIfProtocolsMismatch(SSLTest.java:190)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7702) DistributedAckRegionCCEDUnitTest > testClearOnNonReplicateWithConcurrentEvents is showing a product bug
[
https://issues.apache.org/jira/browse/GEODE-7702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401930#comment-17401930
]
Geode Integration commented on GEODE-7702:
--
Seen on support/1.12 in [distributed-test-openjdk11
#20|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/distributed-test-openjdk11/builds/20]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0266/test-results/distributedTest/1627434205/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0266/test-artifacts/1627434205/distributedtestfiles-openjdk11-1.12.5-build.0266.tgz].
> DistributedAckRegionCCEDUnitTest >
> testClearOnNonReplicateWithConcurrentEvents is showing a product bug
> ---
>
> Key: GEODE-7702
> URL: https://issues.apache.org/jira/browse/GEODE-7702
> Project: Geode
> Issue Type: Bug
> Components: client/server
>Reporter: Mark Hanson
>Assignee: Xiaojian Zhou
>Priority: Major
> Labels: GeodeCommons
> Fix For: 1.14.0
>
>
> testClearOnNonReplicateWithConcurrentEvents in
> DistributedAckRegionCCEDUnitTest.java
> versionTestClearOnNonReplicateWithConcurrentEvents in
> MultiVMRegionTestCase.java
> doOpsLoop
> doOpsLoopNoFlush
> {noformat}
> case 5:
> if (includeClear) {
> CCRegion.clear();
> break;
> } else {
> if (CCRegion.getAttributes().getDataPolicy().withReplication()) {
> if (oldkey != null) {
> CCRegion.putIfAbsent(oldkey, value);
> }
> break;
> } // else fall through to invalidate
> } {noformat}
> the addition of this chunk of code causes this test to fail.
> The core of the problem is that a putall and a clear are happening
> concurrently and the "system" does not respond by either clearing all entries
> or letting all entries persist.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9526) DiskStore test incorrectly treats absolute path as relative on Windows
[
https://issues.apache.org/jira/browse/GEODE-9526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-9526:
--
Labels: pull-request-available (was: )
> DiskStore test incorrectly treats absolute path as relative on Windows
> --
>
> Key: GEODE-9526
> URL: https://issues.apache.org/jira/browse/GEODE-9526
> Project: Geode
> Issue Type: Test
> Components: tests
>Reporter: Dale Emery
>Priority: Major
> Labels: pull-request-available
>
> On Windows, an absolute file path can begin with a letter (e.g. "C:\…").
> {{DiskStoreCommandsDUnitTest.verifyDiskStoreInServer(...)}} incorrectly
> assumes that, because such a path does not start with a file separator, it
> must be relative. It then attempts to convert it to an absolute path by
> prepending the current directory onto it:
> {noformat}
> String absoluteDiskDirectoryName =
> diskDirectoryName.startsWith(File.separator)
> ? diskDirectoryName
> : CURRENT_DIRECTORY + File.separator + diskDirectoryName;
> {noformat}
> On Windows, the resulting file path is unusable.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-6462) [CI Failure] LocatorConnectionDUnitTest > testGetAvailableServersWithStats failed on validateStats
[
https://issues.apache.org/jira/browse/GEODE-6462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401934#comment-17401934
]
Geode Integration commented on GEODE-6462:
--
Seen on support/1.14 in [distributed-test-openjdk8
#22|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/distributed-test-openjdk8/builds/22]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0820/test-results/distributedTest/1625191393/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0820/test-artifacts/1625191393/distributedtestfiles-openjdk8-1.14.0-build.0820.tgz].
> [CI Failure] LocatorConnectionDUnitTest > testGetAvailableServersWithStats
> failed on validateStats
> --
>
> Key: GEODE-6462
> URL: https://issues.apache.org/jira/browse/GEODE-6462
> Project: Geode
> Issue Type: Test
> Components: core
>Reporter: Jens Deppe
>Priority: Major
> Labels: ci
>
> This seems like a flakey test.
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/443]
> The test and the protobuf code has not been updated in a while. This is
> probably a flake.
> The following is the error thread
> {code:java}
> org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest
> > testGetAvailableServersWithStats FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest$$Lambda$37/842046356.run
> in VM 0 running on Host 22c25e73171b with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:406)
> at
> org.apache.geode.test.junit.rules.VMProvider.invoke(VMProvider.java:85)
> at
> org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest.validateStats(LocatorConnectionDUnitTest.java:234)
> at
> org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest.testSocketWithStats(LocatorConnectionDUnitTest.java:127)
> at
> org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest.testGetAvailableServersWithStats(LocatorConnectionDUnitTest.java:106)
> Caused by:
> org.awaitility.core.ConditionTimeoutException: Assertion condition
> defined as a lambda expression in
> org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest
> that uses long, longlong, longlong, longlong, longint, intint expected:<3>
> but was:<4> 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.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest.lambda$validateStats$c7642ca0$1(LocatorConnectionDUnitTest.java:235)
> Caused by:
> java.lang.AssertionError: expected:<3> but was:<4>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:144)
> at
> org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest.lambda$null$0(LocatorConnectionDUnitTest.java:238)
> {code}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>
> [http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-SNAPSHOT.0487/test-results/distributedTest/1551228892/]
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> [http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-SNAPSHOT.0487/test-artifacts/1551228892/distributedtestfiles-OpenJDK8-1.9.0-SNAPSHOT.0487.tgz]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-6183) CI Failure: LocatorLauncherRemoteFileIntegrationTest.startDeletesStaleControlFiles failed with ConditionTimeoutException
[ https://issues.apache.org/jira/browse/GEODE-6183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401935#comment-17401935 ] Geode Integration commented on GEODE-6183: -- Seen on support/1.14 in [integration-test-openjdk11 #25|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/integration-test-openjdk11/builds/25] ... see [test results|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0822/test-results/integrationTest/1625851891/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0822/test-artifacts/1625851891/integrationtestfiles-openjdk11-1.14.0-build.0822.tgz]. > CI Failure: > LocatorLauncherRemoteFileIntegrationTest.startDeletesStaleControlFiles failed > with ConditionTimeoutException > > > Key: GEODE-6183 > URL: https://issues.apache.org/jira/browse/GEODE-6183 > Project: Geode > Issue Type: Bug > Components: build >Reporter: Eric Shu >Assignee: Kirk Lund >Priority: Major > Time Spent: 5h 50m > Remaining Estimate: 0h > > Test failed in > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/IntegrationTestOpenJDK8/builds/223 > org.apache.geode.distributed.LocatorLauncherRemoteFileIntegrationTest > > startDeletesStaleControlFiles FAILED > org.awaitility.core.ConditionTimeoutException: Assertion condition > defined as a lambda expression in > org.apache.geode.distributed.LocatorLauncherRemoteIntegrationTestCase that > uses org.apache.geode.distributed.LocatorLauncher expected:<[online]> but > was:<[not responding]> within 300 seconds. > Caused by: > org.junit.ComparisonFailure: expected:<[online]> but was:<[not > responding]> -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9103) CI Failure: PutAllClientServerDistributedTest.testPutAllReturnsExceptions FAILED
[
https://issues.apache.org/jira/browse/GEODE-9103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401936#comment-17401936
]
Geode Integration commented on GEODE-9103:
--
Seen on support/1.14 in [distributed-test-openjdk11
#26|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/distributed-test-openjdk11/builds/26]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0827/test-results/distributedTest/1626726322/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0827/test-artifacts/1626726322/distributedtestfiles-openjdk11-1.14.0-build.0827.tgz].
> CI Failure: PutAllClientServerDistributedTest.testPutAllReturnsExceptions
> FAILED
>
>
> Key: GEODE-9103
> URL: https://issues.apache.org/jira/browse/GEODE-9103
> Project: Geode
> Issue Type: Bug
> Components: tests
>Affects Versions: 1.15.0
>Reporter: Mark Hanson
>Assignee: Kirk Lund
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
> Fix For: 1.15.0
>
>
> {noformat}
> org.apache.geode.internal.cache.PutAllClientServerDistributedTest >
> testPutAllReturnsExceptions FAILED
> 17:13:44org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.PutAllClientServerDistributedTest$$Lambda$613/835527630.run
> in VM 2 running on Host de2767658753 with 4 VMs
> 17:13:44at
> org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
> 17:13:44at org.apache.geode.test.dunit.VM.invoke(VM.java:448)
> 17:13:44at
> org.apache.geode.internal.cache.PutAllClientServerDistributedTest.testPutAllReturnsExceptions(PutAllClientServerDistributedTest.java:1956)
> 17:13:44
> 17:13:44Caused by:
> 17:13:44java.lang.AssertionError:
> 17:13:44Expecting actual throwable to be an instance of:
> 17:13:44 org.apache.geode.cache.client.ServerOperationException
> 17:13:44but was:
> 17:13:44 org.apache.geode.cache.client.ServerConnectivityException:
> Pool unexpected closed socket on server connection=Pooled Connection to
> de2767658753:36547,172.17.0.10(245):41001: Connection[DESTROYED]).
> Server unreachable: could not connect after 1 attempts
> 17:13:44 at
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:665)
> 17:13:44 at
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:507)
> 17:13:44 at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:157)
> 17:13:44 ...(35 remaining lines not displayed - this can be
> changed with Assertions.setMaxStackTraceElementsDisplayed)
> 17:13:44at
> org.apache.geode.internal.cache.PutAllClientServerDistributedTest.lambda$testPutAllReturnsExceptions$bb17a952$6(PutAllClientServerDistributedTest.java:1961)
> 17:16 {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8117) ServerLauncherRemoteIntegrationTest.startOverwritesStalePidFile fails intermittently
[
https://issues.apache.org/jira/browse/GEODE-8117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401933#comment-17401933
]
Geode Integration commented on GEODE-8117:
--
Seen on support/1.14 in [windows-core-integration-test-openjdk8
#21|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/windows-core-integration-test-openjdk8/builds/21]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0819/test-results/integrationTest/1625131783/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0819/test-artifacts/1625131783/windows-coreintegrationtestfiles-openjdk8-1.14.0-build.0819.tgz].
> ServerLauncherRemoteIntegrationTest.startOverwritesStalePidFile fails
> intermittently
>
>
> Key: GEODE-8117
> URL: https://issues.apache.org/jira/browse/GEODE-8117
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
>
> {noformat}
> org.awaitility.core.ConditionTimeoutException: Assertion condition defined as
> a lambda expression in
> org.apache.geode.distributed.ServerLauncherRemoteIntegrationTestCase
> expected:<[online]> but was:<[not responding]> within 5 minutes.
> at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
> 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:895)
> at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:679)
> at
> org.apache.geode.distributed.ServerLauncherRemoteIntegrationTestCase.awaitStart(ServerLauncherRemoteIntegrationTestCase.java:211)
> at
> org.apache.geode.distributed.ServerLauncherRemoteIntegrationTestCase.awaitStart(ServerLauncherRemoteIntegrationTestCase.java:190)
> at
> org.apache.geode.distributed.ServerLauncherRemoteIntegrationTestCase.awaitStart(ServerLauncherRemoteIntegrationTestCase.java:201)
> at
> org.apache.geode.distributed.ServerLauncherRemoteIntegrationTestCase.startServer(ServerLauncherRemoteIntegrationTestCase.java:131)
> at
> org.apache.geode.distributed.ServerLauncherRemoteIntegrationTestCase.startServer(ServerLauncherRemoteIntegrationTestCase.java:127)
> at
> org.apache.geode.distributed.ServerLauncherRemoteIntegrationTest.startOverwritesStalePidFile(ServerLauncherRemoteIntegrationTest.java:91)
> Caused by: org.junit.ComparisonFailure: expected:<[online]> but was:<[not
> responding]>
> at
> jdk.internal.reflect.GeneratedConstructorAccessor25.newInstance(Unknown
> Source)
> at
> jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.distributed.ServerLauncherRemoteIntegrationTestCase.lambda$awaitStart$1(ServerLauncherRemoteIntegrationTestCase.java:213)
> at
> org.awaitility.core.AssertionCondition.lambda$new$0(AssertionCondition.java:53)
> at
> org.awaitility.core.ConditionAwaiter$ConditionPoller.call(ConditionAwaiter.java:222)
> at
> org.awaitility.core.ConditionAwaiter$ConditionPoller.call(ConditionAwaiter.java:209)
> at java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> ... 1 more
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8825) CI failure: GatewayReceiverMBeanDUnitTest > testMBeanAndProxiesForGatewayReceiverAreRemovedOnDestroy
[
https://issues.apache.org/jira/browse/GEODE-8825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401937#comment-17401937
]
Geode Integration commented on GEODE-8825:
--
Seen on support/1.14 in [distributed-test-openjdk11
#32|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/distributed-test-openjdk11/builds/32]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0838/test-results/distributedTest/1628812269/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0838/test-artifacts/1628812269/distributedtestfiles-openjdk11-1.14.0-build.0838.tgz].
> CI failure: GatewayReceiverMBeanDUnitTest >
> testMBeanAndProxiesForGatewayReceiverAreRemovedOnDestroy
>
>
> Key: GEODE-8825
> URL: https://issues.apache.org/jira/browse/GEODE-8825
> Project: Geode
> Issue Type: Bug
> Components: tests, wan
>Reporter: Jianxia Chen
>Assignee: Barrett Oglesby
>Priority: Major
> Labels: GeodeOperationAPI, flaky, pull-request-available
> Fix For: 1.15.0
>
>
> {code:java}
> org.apache.geode.internal.cache.wan.GatewayReceiverMBeanDUnitTest >
> testMBeanAndProxiesForGatewayReceiverAreRemovedOnDestroy FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.wan.GatewayReceiverMBeanDUnitTest$$Lambda$202/0x0001008f0c40.run
> in VM 0 running on Host c3e48bdac460 with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:623)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:447)
> at
> org.apache.geode.internal.cache.wan.GatewayReceiverMBeanDUnitTest.testMBeanAndProxiesForGatewayReceiverAreRemovedOnDestroy(GatewayReceiverMBeanDUnitTest.java:76)
> Caused by:
> java.lang.AssertionError: expected null, but was: GemFire:service=GatewayReceiver,type=Member,member=172.17.0.18(183)-41002>
> at org.junit.Assert.fail(Assert.java:89)
> at org.junit.Assert.failNotNull(Assert.java:756)
> at org.junit.Assert.assertNull(Assert.java:738)
> at org.junit.Assert.assertNull(Assert.java:748)
> at
> org.apache.geode.internal.cache.wan.GatewayReceiverMBeanDUnitTest.verifyMBeanProxiesDoesNotExist(GatewayReceiverMBeanDUnitTest.java:106)
> at
> org.apache.geode.internal.cache.wan.GatewayReceiverMBeanDUnitTest.lambda$testMBeanAndProxiesForGatewayReceiverAreRemovedOnDestroy$bb17a952$3(GatewayReceiverMBeanDUnitTest.java:76)
> {code}
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/704
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0601/test-results/distributedTest/1610390301/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.14.0-build.0601/test-artifacts/1610390301/distributedtestfiles-OpenJDK11-1.14.0-build.0601.tgz
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9525) Add Radish benchmark tests to CI
[ https://issues.apache.org/jira/browse/GEODE-9525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401939#comment-17401939 ] ASF subversion and git services commented on GEODE-9525: Commit fc6ef7c8e92d0d56d652b496cbf8f2d0fcc07c60 in geode's branch refs/heads/develop from Jens Deppe [ https://gitbox.apache.org/repos/asf?p=geode.git;h=fc6ef7c ] GEODE-9525: Add Radish benchmarks to CI (#6775) - Runs Radish benchmarks on the same topology as the Geode benchmarks (2 x servers, 1 x locator, 1 x client). Current systems are large 72 vCPU instances. - Baseline is taken from when most of the major performance updates have been implemented. > Add Radish benchmark tests to CI > > > Key: GEODE-9525 > URL: https://issues.apache.org/jira/browse/GEODE-9525 > Project: Geode > Issue Type: Test > Components: redis >Reporter: Jens Deppe >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-9525) Add Radish benchmark tests to CI
[ https://issues.apache.org/jira/browse/GEODE-9525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen Nichols reassigned GEODE-9525: --- Assignee: Jens Deppe > Add Radish benchmark tests to CI > > > Key: GEODE-9525 > URL: https://issues.apache.org/jira/browse/GEODE-9525 > Project: Geode > Issue Type: Test > Components: redis >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9525) Add Radish benchmark tests to CI
[ https://issues.apache.org/jira/browse/GEODE-9525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401941#comment-17401941 ] Geode Integration commented on GEODE-9525: -- Seen in [set-pipeline #16|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-meta/jobs/set-pipeline/builds/16]. > Add Radish benchmark tests to CI > > > Key: GEODE-9525 > URL: https://issues.apache.org/jira/browse/GEODE-9525 > Project: Geode > Issue Type: Test > Components: redis >Reporter: Jens Deppe >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9528) CI Failure: DistributionAdvisorIntegrationTest > verifyMembershipListenerIsRemovedAfterForceDisconnect
[
https://issues.apache.org/jira/browse/GEODE-9528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401952#comment-17401952
]
Geode Integration commented on GEODE-9528:
--
Seen on support/1.12 in [integration-test-openjdk11
#29|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/integration-test-openjdk11/builds/29]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0269/test-results/integrationTest/1628816385/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0269/test-artifacts/1628816385/integrationtestfiles-openjdk11-1.12.5-build.0269.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.4
>Reporter: Owen Nichols
>Priority: Major
>
> {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
[
https://issues.apache.org/jira/browse/GEODE-9528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401948#comment-17401948
]
Geode Integration commented on GEODE-9528:
--
Seen on support/1.12 in [integration-test-openjdk11
#23|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/integration-test-openjdk11/builds/23]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0268/test-results/integrationTest/1628309402/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0268/test-artifacts/1628309402/integrationtestfiles-openjdk11-1.12.5-build.0268.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.4
>Reporter: Owen Nichols
>Priority: Major
>
> {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] [Created] (GEODE-9528) CI Failure: DistributionAdvisorIntegrationTest > verifyMembershipListenerIsRemovedAfterForceDisconnect
Owen Nichols created GEODE-9528:
---
Summary: 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.4
Reporter: Owen Nichols
{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
[
https://issues.apache.org/jira/browse/GEODE-9528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401949#comment-17401949
]
Geode Integration commented on GEODE-9528:
--
Seen on support/1.12 in [integration-test-openjdk11
#24|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/integration-test-openjdk11/builds/24]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0268/test-results/integrationTest/1628406705/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0268/test-artifacts/1628406705/integrationtestfiles-openjdk11-1.12.5-build.0268.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.4
>Reporter: Owen Nichols
>Priority: Major
>
> {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
[
https://issues.apache.org/jira/browse/GEODE-9528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401953#comment-17401953
]
Geode Integration commented on GEODE-9528:
--
Seen on support/1.12 in [integration-test-openjdk11
#30|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/integration-test-openjdk11/builds/30]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0269/test-results/integrationTest/1628821241/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0269/test-artifacts/1628821241/integrationtestfiles-openjdk11-1.12.5-build.0269.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.4
>Reporter: Owen Nichols
>Priority: Major
>
> {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
[
https://issues.apache.org/jira/browse/GEODE-9528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401951#comment-17401951
]
Geode Integration commented on GEODE-9528:
--
Seen on support/1.12 in [integration-test-openjdk11
#25|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/integration-test-openjdk11/builds/25]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0268/test-results/integrationTest/1628450069/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0268/test-artifacts/1628450069/integrationtestfiles-openjdk11-1.12.5-build.0268.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.4
>Reporter: Owen Nichols
>Priority: Major
>
> {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] [Updated] (GEODE-9528) CI Failure: DistributionAdvisorIntegrationTest > verifyMembershipListenerIsRemovedAfterForceDisconnect
[
https://issues.apache.org/jira/browse/GEODE-9528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen Nichols updated GEODE-9528:
Labels: blocks-1.12.5 (was: )
> 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.4
>Reporter: Owen Nichols
>Priority: Major
> Labels: blocks-1.12.5
>
> {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
[ https://issues.apache.org/jira/browse/GEODE-8644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401955#comment-17401955 ] Geode Integration commented on GEODE-8644: -- Seen in [distributed-test-openjdk11 #132|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/distributed-test-openjdk11/builds/132] ... see [test results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0421/test-results/distributedTest/1629405868/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0421/test-artifacts/1629405868/distributedtestfiles-openjdk11-1.15.0-build.0421.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-8021) CI Failure: CloseConnectionTest. sharedSenderShouldRecoverFromClosedSocket
[
https://issues.apache.org/jira/browse/GEODE-8021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401956#comment-17401956
]
Geode Integration commented on GEODE-8021:
--
Seen on support/1.12 in [distributed-test-openjdk8
#25|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/distributed-test-openjdk8/builds/25]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0270/test-results/distributedTest/1628850754/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0270/test-artifacts/1628850754/distributedtestfiles-openjdk8-1.12.5-build.0270.tgz].
> CI Failure: CloseConnectionTest. sharedSenderShouldRecoverFromClosedSocket
> --
>
> Key: GEODE-8021
> URL: https://issues.apache.org/jira/browse/GEODE-8021
> Project: Geode
> Issue Type: Bug
> Components: membership
>Affects Versions: 1.12.0
>Reporter: Benjamin P Ross
>Assignee: Bruce J Schuchardt
>Priority: Major
> Fix For: 1.13.0
>
>
> {code:java}
> org.apache.geode.internal.tcp.CloseConnectionTest >
> sharedSenderShouldRecoverFromClosedSocket FAILED
> 16:25:33org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.tcp.CloseConnectionTest$$Lambda$36/1787754664.run
> in VM 1 running on Host 0f261f07755e with 4 VMs
> 16:25:33at
> org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)
> 16:25:33at org.apache.geode.test.dunit.VM.invoke(VM.java:437)
> 16:25:33at
> org.apache.geode.internal.tcp.CloseConnectionTest.sharedSenderShouldRecoverFromClosedSocket(CloseConnectionTest.java:102)
> 16:25:33
> 16:25:33Caused by:
> 16:25:33org.junit.ComparisonFailure: expected:<[tru]e> but
> was:<[fals]e>
> 16:25:33at
> sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> 16:25:33at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> 16:25:33at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> 16:25:33at
> org.apache.geode.internal.tcp.CloseConnectionTest.lambda$sharedSenderShouldRecoverFromClosedSocket$bb17a952$6(CloseConnectionTest.java:109)
> 18:30:47
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9528) CI Failure: DistributionAdvisorIntegrationTest > verifyMembershipListenerIsRemovedAfterForceDisconnect
[
https://issues.apache.org/jira/browse/GEODE-9528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401957#comment-17401957
]
Geode Integration commented on GEODE-9528:
--
Seen on support/1.13 in [integration-test-openjdk11
#37|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-main/jobs/integration-test-openjdk11/builds/37]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.5-build.0575/test-results/integrationTest/1628813862/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.5-build.0575/test-artifacts/1628813862/integrationtestfiles-openjdk11-1.13.5-build.0575.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.4
>Reporter: Owen Nichols
>Priority: Major
> Labels: blocks-1.12.5
>
> {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
[
https://issues.apache.org/jira/browse/GEODE-9528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401958#comment-17401958
]
Geode Integration commented on GEODE-9528:
--
Seen on support/1.14 in [integration-test-openjdk8
#26|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/integration-test-openjdk8/builds/26]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0823/test-results/integrationTest/1626111055/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0823/test-artifacts/1626111055/integrationtestfiles-openjdk8-1.14.0-build.0823.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.4
>Reporter: Owen Nichols
>Priority: Major
> Labels: blocks-1.12.5
>
> {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] [Updated] (GEODE-9528) CI Failure: DistributionAdvisorIntegrationTest > verifyMembershipListenerIsRemovedAfterForceDisconnect
[
https://issues.apache.org/jira/browse/GEODE-9528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen Nichols updated GEODE-9528:
Affects Version/s: (was: 1.12.4)
1.14.0
1.13.5
1.12.5
> 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
>
> {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] [Updated] (GEODE-9528) CI Failure: DistributionAdvisorIntegrationTest > verifyMembershipListenerIsRemovedAfterForceDisconnect
[
https://issues.apache.org/jira/browse/GEODE-9528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen Nichols updated GEODE-9528:
Labels: blocks-1.12.5 blocks-1.13.5 blocks-1.14.0 (was: blocks-1.12.5)
> 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-9280) CI Failure: ClientServerMiscBCDUnitTest > testSubscriptionWithMixedServersAndOldClientFeed[0] FAILED
[
https://issues.apache.org/jira/browse/GEODE-9280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401959#comment-17401959
]
Geode Integration commented on GEODE-9280:
--
Seen on support/1.14 in [upgrade-test-openjdk8
#28|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/upgrade-test-openjdk8/builds/28]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0827/test-results/upgradeTest/1626734943/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0827/test-artifacts/1626734943/upgradetestfiles-openjdk8-1.14.0-build.0827.tgz].
> CI Failure: ClientServerMiscBCDUnitTest >
> testSubscriptionWithMixedServersAndOldClientFeed[0] FAILED
>
>
> Key: GEODE-9280
> URL: https://issues.apache.org/jira/browse/GEODE-9280
> Project: Geode
> Issue Type: Test
> Components: ci, client/server
>Reporter: Jens Deppe
>Priority: Major
>
> {noformat}
> org.apache.geode.internal.cache.tier.sockets.ClientServerMiscBCDUnitTest >
> testSubscriptionWithMixedServersAndOldClientFeed[0] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.test.dunit.internal.IdentifiableRunnable.run in VM 4 running
> on Host ca88a5f241e5 with 5 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:435)
> at
> org.apache.geode.internal.cache.tier.sockets.ClientServerMiscBCDUnitTest.doTestSubscriptionWithMixedServersAndPeerFeed(ClientServerMiscBCDUnitTest.java:249)
> at
> org.apache.geode.internal.cache.tier.sockets.ClientServerMiscBCDUnitTest.testSubscriptionWithMixedServersAndOldClientFeed(ClientServerMiscBCDUnitTest.java:177)
> Caused by:
> java.util.NoSuchElementException
> at
> java.util.concurrent.ConcurrentHashMap$ValueIterator.next(ConcurrentHashMap.java:3436)
> at
> java.util.Collections$UnmodifiableCollection$1.next(Collections.java:1044)
> at
> org.apache.geode.internal.cache.tier.sockets.ClientServerMiscBCDUnitTest.lambda$doTestSubscriptionWithMixedServersAndPeerFeed$60ce2e92$7(ClientServerMiscBCDUnitTest.java:251)
> {noformat}
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0244/test-results/upgradeTest/1621094517/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0244/test-artifacts/1621094517/upgradetestfiles-OpenJDK8-1.15.0-build.0244.tgz
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-6819) CI failure: PartitionedRegionSingleHopDUnitTest. testMetadataIsSameOnAllServersAndClients
[
https://issues.apache.org/jira/browse/GEODE-6819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17402019#comment-17402019
]
Geode Integration commented on GEODE-6819:
--
Seen on support/1.13 in [DistributedTestOpenJDK8
#69|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-13-main/jobs/DistributedTestOpenJDK8/builds/69]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.2-build.0452/test-results/distributedTest/1610765666/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-13-main/1.13.2-build.0452/test-artifacts/1610765666/distributedtestfiles-OpenJDK8-1.13.2-build.0452.tgz].
> 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: Kirk Lund
>Priority: Major
> Labels: flaky
> Fix For: 1.13.0
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> {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)
