[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=17403216#comment-17403216 ] ASF subversion and git services commented on GEODE-9525: Commit dc18a2a75c09452ed3394ef50a4c8229da1bd8ec in geode's branch refs/heads/develop from Jens Deppe [ https://gitbox.apache.org/repos/asf?p=geode.git;h=dc18a2a ] GEODE-9525: Add Radish benchmarks to CI - fix 2 (#6784) > 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-9535) CI Failure: Tomcat7ClientServerTest > newContainersShouldShareDataAccess
[
https://issues.apache.org/jira/browse/GEODE-9535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17403248#comment-17403248
]
Geode Integration commented on GEODE-9535:
--
Seen in [distributed-test-openjdk8
#1387|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/1387]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0426/test-results/distributedTest/1629582590/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0426/test-artifacts/1629582590/distributedtestfiles-openjdk8-1.15.0-build.0426.tgz].
> CI Failure: Tomcat7ClientServerTest > newContainersShouldShareDataAccess
>
>
> Key: GEODE-9535
> URL: https://issues.apache.org/jira/browse/GEODE-9535
> Project: Geode
> Issue Type: Test
> Components: http session
>Reporter: Jens Deppe
>Priority: Major
>
> https://hydradb.hdb.gemfire-ci.info/hdb/testresult/11328748
> {noformat}
> > Task :geode-assembly:distributedTest
> org.apache.geode.session.tests.Tomcat7ClientServerTest >
> newContainersShouldShareDataAccess FAILED
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in 'dunit_suspect-vm0.log' at line 423
> [fatal 2021/08/21 21:05:18.691 UTC tid=855]
> Exception in processing request from 10.0.0.108
> java.lang.Exception: Improperly configured client detected - use
> addPoolLocator to configure its locators instead of addPoolServer.
> at
> org.apache.geode.distributed.internal.ProtocolCheckerImpl.checkProtocol(ProtocolCheckerImpl.java:31)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:342)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> ---
> Found suspect string in 'dunit_suspect-vm0.log' at line 540
> [fatal 2021/08/21 21:05:30.875 UTC tid=855]
> Exception in processing request from 10.0.0.108
> java.lang.Exception: Improperly configured client detected - use
> addPoolLocator to configure its locators instead of addPoolServer.
> at
> org.apache.geode.distributed.internal.ProtocolCheckerImpl.checkProtocol(ProtocolCheckerImpl.java:31)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:342)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> 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.TestWatcher$1.evaluate(TestWatcher.java:61)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at
> org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
> at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at
> org.gradle.api.intern
[jira] [Created] (GEODE-9535) CI Failure: Tomcat7ClientServerTest > newContainersShouldShareDataAccess
Jens Deppe created GEODE-9535:
-
Summary: CI Failure: Tomcat7ClientServerTest >
newContainersShouldShareDataAccess
Key: GEODE-9535
URL: https://issues.apache.org/jira/browse/GEODE-9535
Project: Geode
Issue Type: Test
Components: http session
Reporter: Jens Deppe
https://hydradb.hdb.gemfire-ci.info/hdb/testresult/11328748
{noformat}
> Task :geode-assembly:distributedTest
org.apache.geode.session.tests.Tomcat7ClientServerTest >
newContainersShouldShareDataAccess FAILED
java.lang.AssertionError: Suspicious strings were written to the log during
this run.
Fix the strings or use IgnoredException.addIgnoredException to ignore.
---
Found suspect string in 'dunit_suspect-vm0.log' at line 423
[fatal 2021/08/21 21:05:18.691 UTC tid=855]
Exception in processing request from 10.0.0.108
java.lang.Exception: Improperly configured client detected - use
addPoolLocator to configure its locators instead of addPoolServer.
at
org.apache.geode.distributed.internal.ProtocolCheckerImpl.checkProtocol(ProtocolCheckerImpl.java:31)
at
org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:342)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
---
Found suspect string in 'dunit_suspect-vm0.log' at line 540
[fatal 2021/08/21 21:05:30.875 UTC tid=855]
Exception in processing request from 10.0.0.108
java.lang.Exception: Improperly configured client detected - use
addPoolLocator to configure its locators instead of addPoolServer.
at
org.apache.geode.distributed.internal.ProtocolCheckerImpl.checkProtocol(ProtocolCheckerImpl.java:31)
at
org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:342)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
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.TestWatcher$1.evaluate(TestWatcher.java:61)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at
org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
at
org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:62)
at
org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.gr
[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 ] ASF GitHub Bot updated GEODE-9521: -- Labels: GeodeOperationAPI pull-request-available security (was: GeodeOperationAPI security) > 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, pull-request-available, security > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17403253#comment-17403253 ] ASF subversion and git services commented on GEODE-9521: Commit e4f8e8eb4930ae2748a6b9f3f64bd267ca7d9eb3 in geode's branch refs/heads/expireAuthentication from Jinmei Liao [ https://gitbox.apache.org/repos/asf?p=geode.git;h=e4f8e8e ] GEODE-9521: Add test to cover multi-servers scenario for re-authentic… (#6782) > 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, pull-request-available, security > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-9531) CI Failure: TxCommitMessageBCClientToServerTxPartitionTest fails with ForcedDisconnectException
[
https://issues.apache.org/jira/browse/GEODE-9531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Shu reassigned GEODE-9531:
---
Assignee: Eric Shu
> CI Failure: TxCommitMessageBCClientToServerTxPartitionTest fails with
> ForcedDisconnectException
> ---
>
> Key: GEODE-9531
> URL: https://issues.apache.org/jira/browse/GEODE-9531
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Donal Evans
>Assignee: Eric Shu
>Priority: Major
> Labels: blocks-1.14.0
>
> {noformat}
> org.apache.geode.internal.cache.TxCommitMessageBCClientToServerTxPartitionTest
> > test[11] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.TxCommitMessageBCTestBase$$Lambda$55/2050040059.run
> in VM 2 running on Host 1797ac7f43c4 with 5 VMs
> Caused by:
> org.apache.geode.distributed.DistributedSystemDisconnectedException:
> membership shutdown, caused by org.apache.geode.ForcedDisconnectException:
> Member isn't responding to heartbeat requests
> Caused by:
> org.apache.geode.ForcedDisconnectException: Member isn't
> responding to heartbeat requests
> 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-vm2.log' at line 993
> [fatal 2021/05/25 16:58:13.700 GMT
> tid=1349] Membership service failure: Member isn't responding to heartbeat
> requests
>
> org.apache.geode.distributed.internal.membership.api.MemberDisconnectedException:
> Member isn't responding to heartbeat requests
> at
> org.apache.geode.distributed.internal.membership.gms.GMSMembership$ManagerImpl.forceDisconnect(GMSMembership.java:1783)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.forceDisconnect(GMSJoinLeave.java:1122)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.processRemoveMemberMessage(GMSJoinLeave.java:725)
> at
> org.apache.geode.distributed.internal.membership.gms.messenger.JGroupsMessenger$JGroupsReceiver.receive(JGroupsMessenger.java:1366)
> at
> org.apache.geode.distributed.internal.membership.gms.messenger.JGroupsMessenger$JGroupsReceiver.receive(JGroupsMessenger.java:1302)
> at org.jgroups.JChannel.invokeCallback(JChannel.java:816)
> at org.jgroups.JChannel.up(JChannel.java:741)
> at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:1030)
> at org.jgroups.protocols.FRAG2.up(FRAG2.java:165)
> at org.jgroups.protocols.FlowControl.up(FlowControl.java:390)
> at org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1077)
> at org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:792)
> at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:433)
> at
> org.apache.geode.distributed.internal.membership.gms.messenger.StatRecorder.up(StatRecorder.java:72)
> at
> org.apache.geode.distributed.internal.membership.gms.messenger.AddressManager.up(AddressManager.java:70)
> at org.jgroups.protocols.TP.passMessageUp(TP.java:1658)
> at org.jgroups.protocols.TP$SingleMessageHandler.run(TP.java:1876)
> at org.jgroups.util.DirectExecutor.execute(DirectExecutor.java:10)
> at org.jgroups.protocols.TP.handleSingleMessage(TP.java:1789)
> at org.jgroups.protocols.TP.receive(TP.java:1714)
> at
> org.apache.geode.distributed.internal.membership.gms.messenger.Transport.receive(Transport.java:159)
> at org.jgroups.protocols.UDP$PacketReceiver.run(UDP.java:701)
> at java.lang.Thread.run(Thread.java:748)
> ---
> Found suspect string in 'dunit_suspect-vm2.log' at line 1041
> [error 2021/05/25 16:58:14.206 GMT
> tid=135] Cache initialization for GemFireCache[id = 664332017; isClosing =
> false; isShutDownAll = false; created = Tue May 25 16:57:54 GMT 2021; server
> = false; copyOnRead = false; lockLease = 120; lockTimeout = 60] failed
> because:
> org.apache.geode.distributed.DistributedSystemDisconnectedException:
> membership shutdown, caused by org.apache.geode.ForcedDisconnectException:
> Member isn't responding to heartbeat requests
> at
> org.apache.geode.distributed.internal.DistributionImpl.checkCancelled(DistributionImpl.java:313)
> at
> org.apache.geode.distributed.internal.DistributionImpl.send(DistributionImpl.java:243)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.sendViaMembership
[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=17403266#comment-17403266 ] ASF subversion and git services commented on GEODE-9525: Commit 9fcbb743cfdd57bff1ba40b10639e769148b5cc3 in geode's branch refs/heads/expireAuthentication from Jens Deppe [ https://gitbox.apache.org/repos/asf?p=geode.git;h=9fcbb74 ] GEODE-9525: Add Radish benchmarks to CI - with fix (#6780) > 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-9523) ContainerInstall Resource path invalid on Windows
[
https://issues.apache.org/jira/browse/GEODE-9523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17403267#comment-17403267
]
ASF subversion and git services commented on GEODE-9523:
Commit 2752849e28711f27fdc41556984358583b5fc012 in geode's branch
refs/heads/expireAuthentication from Dale Emery
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=2752849 ]
GEODE-9523: Fix invalid path in ContainerInstall (#6774)
PROBLEM
`ContainerInstall` fetches a resource URL, then applies a chain of
conversions before passing the resulting URL to the `ZipURLInstaller`
constructor. One of the conversions attempts to create a `Path` from a
string. On Windows, the string value is not a valid path, and
`Paths.get(...)` throws an exception.
SOLUTION
Change `ContainerInstall` to remove all of the conversions. The original
resource URL is acceptable to `ZipURLInstaller` without any conversion.
> 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
> Fix For: 1.15.0
>
>
> 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-9514) reduce object allocations when Coder writes "int" and "long" values
[ https://issues.apache.org/jira/browse/GEODE-9514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17403265#comment-17403265 ] ASF subversion and git services commented on GEODE-9514: Commit 1969f3965092756fe1e5ba0dab89790f498c3893 in geode's branch refs/heads/expireAuthentication from Darrel Schneider [ https://gitbox.apache.org/repos/asf?p=geode.git;h=1969f39 ] GEODE-9514: optimize how Coder reads and writes "int" and "long" values (#6765) * added appendAsciiDigitsToByteBuf to Coder so that ints and longs can more efficiently by added to a ByteBuf. The goal was to reduce the number of short lived object allocations. * longToBytes and intToBytes now use the new conversion code and for small numbers canonical arrays are used * bytesToLong optimized to not convert the byte array to a String * getBulkStringResponse now uses getIntegerResponse This method no longer truncates a Long to an Integer > reduce object allocations when Coder writes "int" and "long" values > --- > > Key: GEODE-9514 > URL: https://issues.apache.org/jira/browse/GEODE-9514 > Project: Geode > Issue Type: Improvement > Components: redis >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > Refactor the Coder.getIntegerResponse(ByteBuf buffer, long l) method to write > byte string representation to avoid allocating transient char[], String, and > byte[]. The existing allocations accounted for 17% of objects requiring GC. -- 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=17403270#comment-17403270 ] ASF subversion and git services commented on GEODE-9525: Commit dc18a2a75c09452ed3394ef50a4c8229da1bd8ec in geode's branch refs/heads/expireAuthentication from Jens Deppe [ https://gitbox.apache.org/repos/asf?p=geode.git;h=dc18a2a ] GEODE-9525: Add Radish benchmarks to CI - fix 2 (#6784) > 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-9529) fix release scripts
[ https://issues.apache.org/jira/browse/GEODE-9529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17403269#comment-17403269 ] ASF subversion and git services commented on GEODE-9529: Commit 9ff39d12361e668657413b8cbfc9558b71795a96 in geode's branch refs/heads/expireAuthentication from Owen Nichols [ https://gitbox.apache.org/repos/asf?p=geode.git;h=9ff39d12 ] GEODE-9529: fix release scripts (benchmark baseline, docker) (#6779) * update benchmark baseline on support branch on new minor release * make it clear that Dockerfile on develop is a template, and can only be used to build a Geode image from a released support branch * change end-of-support message to version-based not time-based > fix release scripts > --- > > Key: GEODE-9529 > URL: https://issues.apache.org/jira/browse/GEODE-9529 > Project: Geode > Issue Type: Improvement > Components: release >Reporter: Owen Nichols >Assignee: Owen Nichols >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > * update benchmark baseline on support branch on new minor release > * change end-of-support message to version-based not time-based > * fix typo in Dockerfile > * make it clear that Dockerfile on develop is a template, not actually > buildable except on a support branch after it has had at least one release -- 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=17403264#comment-17403264 ] ASF subversion and git services commented on GEODE-9525: Commit fc6ef7c8e92d0d56d652b496cbf8f2d0fcc07c60 in geode's branch refs/heads/expireAuthentication 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 >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17403268#comment-17403268
]
ASF subversion and git services commented on GEODE-9526:
Commit 0d1954bbabccf7cc466392c48ecfd82df664b1b9 in geode's branch
refs/heads/expireAuthentication from Dale Emery
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=0d1954b ]
GEODE-9526: Fix path computation in DiskStore test (#6777)
PROBLEM
`DiskStoreCommandsDUnitTest.verifyDiskStoreInServer(...)` incorrectly
assumes thatif a file path does not start with a file separator, it must
be relative. It attempts to convert such a path to absolute by
prepending the current directory onto it:
```
String absoluteDiskDirectoryName = diskDirectoryName.startsWith(File.separator)
? diskDirectoryName
: CURRENT_DIRECTORY + File.separator + diskDirectoryName;
```
On Windows, an absolute file path can begin with a letter, e.g.
`C:\Users\geode\AppData\Local\Temp\junit783716437098694709\DISKSTORE`.
The test incorrectly interprets a path like this as relative, and
prepends the current directory onto it, producing an invalid path. It
then uses this incorrect path in an assertion, causing the test to fail
when it should pass.
SOLUTION
Use Java's `Path` implementation for the OS to compute the absolute form of the
given file path.
> 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
>Assignee: Dale Emery
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
> Fix For: 1.15.0
>
>
> 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-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=17403271#comment-17403271 ] ASF subversion and git services commented on GEODE-9456: Commit c79b75681f6530380d64dcf86f5561d02a0f432c in geode's branch refs/heads/expireAuthentication from Jinmei Liao [ https://gitbox.apache.org/repos/asf?p=geode.git;h=c79b756 ] 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-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:comment-tabpanel&focusedCommentId=17403273#comment-17403273 ] ASF subversion and git services commented on GEODE-9460: Commit 8507bed1c7b182791c50eb5b96029d0f6a29b9d9 in geode's branch refs/heads/expireAuthentication from Joris Melchior [ https://gitbox.apache.org/repos/asf?p=geode.git;h=8507bed ] GEODE-9460: Add testing for mutli-user scenarios (#6755) Co-Authored-By Jinmei Liao > 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] [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=17403272#comment-17403272 ] ASF subversion and git services commented on GEODE-9452: Commit c79b75681f6530380d64dcf86f5561d02a0f432c in geode's branch refs/heads/expireAuthentication from Jinmei Liao [ https://gitbox.apache.org/repos/asf?p=geode.git;h=c79b756 ] 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] [Commented] (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:comment-tabpanel&focusedCommentId=17403274#comment-17403274 ] ASF subversion and git services commented on GEODE-9521: Commit 5bbd1c9e33b130f0ae0eec77bf7316681a457714 in geode's branch refs/heads/expireAuthentication from Jinmei Liao [ https://gitbox.apache.org/repos/asf?p=geode.git;h=5bbd1c9 ] GEODE-9521: Add test to cover multi-servers scenario for re-authentic… (#6782) > 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, pull-request-available, security > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9533) CI Failure: RedisSessionDUnitTest fails due to BindException
[
https://issues.apache.org/jira/browse/GEODE-9533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donal Evans updated GEODE-9533:
---
Labels: redis (was: )
> CI Failure: RedisSessionDUnitTest fails due to BindException
>
>
> Key: GEODE-9533
> URL: https://issues.apache.org/jira/browse/GEODE-9533
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Donal Evans
>Priority: Major
> Labels: redis
>
> {noformat}
> org.apache.geode.redis.session.RedisSessionDUnitTest > classMethod FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.test.dunit.internal.IdentifiableRunnable.run in VM 4 running
> on Host 2c546f86e3dc 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.redis.session.SessionDUnitTest.startSpringApp(SessionDUnitTest.java:146)
> at
> org.apache.geode.redis.session.SessionDUnitTest.setupSpringApps(SessionDUnitTest.java:104)
> at
> org.apache.geode.redis.session.RedisSessionDUnitTest.setup(RedisSessionDUnitTest.java:42)
> Caused by:
> org.springframework.context.ApplicationContextException: Failed to
> start bean 'webServerStartStop'; nested exception is
> org.springframework.boot.web.server.PortInUseException: Port 22500 is already
> in use
> Caused by:
> org.springframework.boot.web.server.PortInUseException: Port
> 22500 is already in use
> Caused by:
> java.io.IOException: Failed to bind to /0.0.0.0:22500
> Caused by:
> java.net.BindException: Address already in use
> org.apache.geode.redis.session.RedisSessionDUnitTest > classMethod FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.redis.session.SessionDUnitTest$$Lambda$166/1957083485.run in
> VM 4 running on Host 2c546f86e3dc with 5 VMs
> Caused by:
> java.lang.NullPointerException
> 114 tests completed, 2 failed
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0837/test-results/distributedTest/1628717583/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0837/test-artifacts/1628717583/distributedtestfiles-openjdk8-1.14.0-build.0837.tgz
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-9536) Run all Windows distributed tests in CI, in parallel
Dale Emery created GEODE-9536: - Summary: Run all Windows distributed tests in CI, in parallel Key: GEODE-9536 URL: https://issues.apache.org/jira/browse/GEODE-9536 Project: Geode Issue Type: Test Components: ci, tests Reporter: Dale Emery Currently CI runs only a subset of distributed tests on Windows, and it runs them sequentially. Change CI to run all distributed tests in Windows, and to run them in parallel. This requires changing a small number tests to allow them to run on Windows. It may require additional changes to allow them to run in parallel on Windows. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-9536) Run all Windows distributed tests in CI, in parallel
[ https://issues.apache.org/jira/browse/GEODE-9536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale Emery reassigned GEODE-9536: - Assignee: Dale Emery > Run all Windows distributed tests in CI, in parallel > > > Key: GEODE-9536 > URL: https://issues.apache.org/jira/browse/GEODE-9536 > Project: Geode > Issue Type: Test > Components: ci, tests >Reporter: Dale Emery >Assignee: Dale Emery >Priority: Major > Labels: GeodeOperationAPI > > Currently CI runs only a subset of distributed tests on Windows, and it runs > them sequentially. > Change CI to run all distributed tests in Windows, and to run them in > parallel. > This requires changing a small number tests to allow them to run on Windows. > It may require additional changes to allow them to run in parallel on Windows. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9536) Run all Windows distributed tests in CI, in parallel
[ https://issues.apache.org/jira/browse/GEODE-9536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dale Emery updated GEODE-9536: -- Labels: GeodeOperationAPI (was: ) > Run all Windows distributed tests in CI, in parallel > > > Key: GEODE-9536 > URL: https://issues.apache.org/jira/browse/GEODE-9536 > Project: Geode > Issue Type: Test > Components: ci, tests >Reporter: Dale Emery >Priority: Major > Labels: GeodeOperationAPI > > Currently CI runs only a subset of distributed tests on Windows, and it runs > them sequentially. > Change CI to run all distributed tests in Windows, and to run them in > parallel. > This requires changing a small number tests to allow them to run on Windows. > It may require additional changes to allow them to run in parallel on Windows. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-9532) CI Failure: DiskDistributedNoAckAsyncRegionDUnitTest > testNoDataSerializer fails with NotSerializableException
[
https://issues.apache.org/jira/browse/GEODE-9532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jianxia Chen reassigned GEODE-9532:
---
Assignee: Jianxia Chen
> CI Failure: DiskDistributedNoAckAsyncRegionDUnitTest > testNoDataSerializer
> fails with NotSerializableException
> ---
>
> Key: GEODE-9532
> URL: https://issues.apache.org/jira/browse/GEODE-9532
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Donal Evans
>Assignee: Jianxia Chen
>Priority: Major
> Labels: blocks-1.14.0
>
> {noformat}
> org.apache.geode.cache30.DiskDistributedNoAckAsyncRegionDUnitTest >
> testNoDataSerializer FAILED
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in 'dunit_suspect-vm0.log' at line 570
> [fatal 2021/06/15 17:11:03.722 GMT DiskDistributedNoAckAsyncRegionDUnitTest_testNoDataSerializer> tid=2145]
> Fatal error from asynchronous flusher thread
> org.apache.geode.SerializationException: An IOException was thrown while
> serializing.
> at
> org.apache.geode.internal.cache.EntryEventImpl.serialize(EntryEventImpl.java:2105)
> at
> org.apache.geode.internal.cache.EntryEventImpl.serialize(EntryEventImpl.java:2088)
> at
> org.apache.geode.internal.cache.VMCachedDeserializable.getSerializedValue(VMCachedDeserializable.java:200)
> at
> org.apache.geode.internal.cache.entries.DiskEntry$Helper.createValueWrapper(DiskEntry.java:753)
> at
> org.apache.geode.internal.cache.entries.DiskEntry$Helper.createValueWrapperFromEntry(DiskEntry.java:807)
> at
> org.apache.geode.internal.cache.entries.DiskEntry$Helper.writeToDisk(DiskEntry.java:825)
> at
> org.apache.geode.internal.cache.entries.DiskEntry$Helper.writeToDisk(DiskEntry.java:815)
> at
> org.apache.geode.internal.cache.entries.DiskEntry$Helper.writeEntryToDisk(DiskEntry.java:1493)
> at
> org.apache.geode.internal.cache.entries.DiskEntry$Helper.doAsyncFlush(DiskEntry.java:1445)
> at
> org.apache.geode.internal.cache.DiskStoreImpl$FlusherThread.doAsyncFlush(DiskStoreImpl.java:1765)
> at
> org.apache.geode.internal.cache.DiskStoreImpl$FlusherThread.run(DiskStoreImpl.java:1723)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.io.NotSerializableException:
> org.apache.geode.cache30.MultiVMRegionTestCase$LongWrapper
> at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1184)
> at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348)
> at
> org.apache.geode.internal.InternalDataSerializer.writeSerializableObject(InternalDataSerializer.java:2186)
> at
> org.apache.geode.internal.InternalDataSerializer.basicWriteObject(InternalDataSerializer.java:2055)
> at org.apache.geode.DataSerializer.writeObject(DataSerializer.java:2839)
> at
> org.apache.geode.internal.util.BlobHelper.serializeToBlob(BlobHelper.java:54)
> at
> org.apache.geode.internal.cache.EntryEventImpl.serialize(EntryEventImpl.java:2103)
> ... 11 more
> ---
> Found suspect string in 'dunit_suspect-vm0.log' at line 594
> [error 2021/06/15 17:11:03.734 GMT DiskDistributedNoAckAsyncRegionDUnitTest_testNoDataSerializer> tid=2145] A
> DiskAccessException has occurred while writing to the disk for disk store
> DiskDistributedNoAckAsyncRegionDUnitTest_testNoDataSerializer. The cache will
> be closed.
> org.apache.geode.cache.DiskAccessException: For DiskStore:
> DiskDistributedNoAckAsyncRegionDUnitTest_testNoDataSerializer: Fatal error
> from asynchronous flusher thread, caused by
> org.apache.geode.SerializationException: An IOException was thrown while
> serializing.
> at
> org.apache.geode.internal.cache.DiskStoreImpl$FlusherThread.doAsyncFlush(DiskStoreImpl.java:1809)
> at
> org.apache.geode.internal.cache.DiskStoreImpl$FlusherThread.run(DiskStoreImpl.java:1723)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.apache.geode.SerializationException: An IOException was
> thrown while serializing.
> at
> org.apache.geode.internal.cache.EntryEventImpl.serialize(EntryEventImpl.java:2105)
> at
> org.apache.geode.internal.cache.EntryEventImpl.serialize(EntryEventImpl.java:2088)
> at
> org.apache.geode.internal.cache.VMCachedDeserializable.getSerializedValue(VMCachedDeserializable.java:200)
> at
> org.apache.geode.internal.cache.entries.DiskEntry$Helper.createValueWrapper(
[jira] [Updated] (GEODE-9532) CI Failure: DiskDistributedNoAckAsyncRegionDUnitTest > testNoDataSerializer fails with NotSerializableException
[
https://issues.apache.org/jira/browse/GEODE-9532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jianxia Chen updated GEODE-9532:
Labels: GeodeOperationAPI blocks-1.14.0 (was: blocks-1.14.0)
> CI Failure: DiskDistributedNoAckAsyncRegionDUnitTest > testNoDataSerializer
> fails with NotSerializableException
> ---
>
> Key: GEODE-9532
> URL: https://issues.apache.org/jira/browse/GEODE-9532
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Donal Evans
>Assignee: Jianxia Chen
>Priority: Major
> Labels: GeodeOperationAPI, blocks-1.14.0
>
> {noformat}
> org.apache.geode.cache30.DiskDistributedNoAckAsyncRegionDUnitTest >
> testNoDataSerializer FAILED
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in 'dunit_suspect-vm0.log' at line 570
> [fatal 2021/06/15 17:11:03.722 GMT DiskDistributedNoAckAsyncRegionDUnitTest_testNoDataSerializer> tid=2145]
> Fatal error from asynchronous flusher thread
> org.apache.geode.SerializationException: An IOException was thrown while
> serializing.
> at
> org.apache.geode.internal.cache.EntryEventImpl.serialize(EntryEventImpl.java:2105)
> at
> org.apache.geode.internal.cache.EntryEventImpl.serialize(EntryEventImpl.java:2088)
> at
> org.apache.geode.internal.cache.VMCachedDeserializable.getSerializedValue(VMCachedDeserializable.java:200)
> at
> org.apache.geode.internal.cache.entries.DiskEntry$Helper.createValueWrapper(DiskEntry.java:753)
> at
> org.apache.geode.internal.cache.entries.DiskEntry$Helper.createValueWrapperFromEntry(DiskEntry.java:807)
> at
> org.apache.geode.internal.cache.entries.DiskEntry$Helper.writeToDisk(DiskEntry.java:825)
> at
> org.apache.geode.internal.cache.entries.DiskEntry$Helper.writeToDisk(DiskEntry.java:815)
> at
> org.apache.geode.internal.cache.entries.DiskEntry$Helper.writeEntryToDisk(DiskEntry.java:1493)
> at
> org.apache.geode.internal.cache.entries.DiskEntry$Helper.doAsyncFlush(DiskEntry.java:1445)
> at
> org.apache.geode.internal.cache.DiskStoreImpl$FlusherThread.doAsyncFlush(DiskStoreImpl.java:1765)
> at
> org.apache.geode.internal.cache.DiskStoreImpl$FlusherThread.run(DiskStoreImpl.java:1723)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.io.NotSerializableException:
> org.apache.geode.cache30.MultiVMRegionTestCase$LongWrapper
> at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1184)
> at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348)
> at
> org.apache.geode.internal.InternalDataSerializer.writeSerializableObject(InternalDataSerializer.java:2186)
> at
> org.apache.geode.internal.InternalDataSerializer.basicWriteObject(InternalDataSerializer.java:2055)
> at org.apache.geode.DataSerializer.writeObject(DataSerializer.java:2839)
> at
> org.apache.geode.internal.util.BlobHelper.serializeToBlob(BlobHelper.java:54)
> at
> org.apache.geode.internal.cache.EntryEventImpl.serialize(EntryEventImpl.java:2103)
> ... 11 more
> ---
> Found suspect string in 'dunit_suspect-vm0.log' at line 594
> [error 2021/06/15 17:11:03.734 GMT DiskDistributedNoAckAsyncRegionDUnitTest_testNoDataSerializer> tid=2145] A
> DiskAccessException has occurred while writing to the disk for disk store
> DiskDistributedNoAckAsyncRegionDUnitTest_testNoDataSerializer. The cache will
> be closed.
> org.apache.geode.cache.DiskAccessException: For DiskStore:
> DiskDistributedNoAckAsyncRegionDUnitTest_testNoDataSerializer: Fatal error
> from asynchronous flusher thread, caused by
> org.apache.geode.SerializationException: An IOException was thrown while
> serializing.
> at
> org.apache.geode.internal.cache.DiskStoreImpl$FlusherThread.doAsyncFlush(DiskStoreImpl.java:1809)
> at
> org.apache.geode.internal.cache.DiskStoreImpl$FlusherThread.run(DiskStoreImpl.java:1723)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.apache.geode.SerializationException: An IOException was
> thrown while serializing.
> at
> org.apache.geode.internal.cache.EntryEventImpl.serialize(EntryEventImpl.java:2105)
> at
> org.apache.geode.internal.cache.EntryEventImpl.serialize(EntryEventImpl.java:2088)
> at
> org.apache.geode.internal.cache.VMCachedDeserializable.getSerializedValue(VMCachedDeserializable.java:200)
> at
> org.apache.geode.intern
[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=17403301#comment-17403301
]
ASF subversion and git services commented on GEODE-9071:
Commit 018fb585b1750a3186ad4693744ed5630d869182 in geode's branch
refs/heads/develop from Eric Shu
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=018fb58 ]
GEODE-9071: Add wait before check cq listener invocations. (#6785)
* Cq events sent to client asynchronously. Need to wait events are
all delivered.
> 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
>Assignee: Eric Shu
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
>
> {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] [Updated] (GEODE-9482) Radish commands do not match Redis error behaviour for integer arguments beginning "-0" and "+"
[
https://issues.apache.org/jira/browse/GEODE-9482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donal Evans updated GEODE-9482:
---
Description:
When using native Redis, commands that take integer arguments return {{"ERR
value is not an integer or out of range"}} if the argument begins with "-0" or
"+". The current implementation of these commands in Geode does not behave the
same way.
The {{Coder.bytesToLong()}} method should be modified to check for the first
two characters being "-0" or "+" and throw a {{NumberFormatException}} if that
is the case. Alternately, if there are places where we want to preserve the
existing behaviour of {{Coder.bytesToLong()}}, an additional
{{bytesToLongStrict()}} method could be added to the {{Coder}} class with this
additional check.
was:
When using native Redis, commands that take integer arguments return {{"ERR
value is not an integer or out of range"}} if the argument begins with "-0".
The current implementation of these commands in Geode does not behave the same
way.
The {{Coder.bytesToLong()}} method should be modified to check for the first
two characters being "-0" and throw a {{NumberFormatException}} if that is the
case. Alternately, if there are places where we want to preserve the existing
behaviour of {{Coder.bytesToLong()}}, an additional {{bytesToLongStrict()}}
method could be added to the {{Coder}} class with this additional check.
> Radish commands do not match Redis error behaviour for integer arguments
> beginning "-0" and "+"
> ---
>
> Key: GEODE-9482
> URL: https://issues.apache.org/jira/browse/GEODE-9482
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Priority: Major
>
> When using native Redis, commands that take integer arguments return {{"ERR
> value is not an integer or out of range"}} if the argument begins with "-0"
> or "+". The current implementation of these commands in Geode does not behave
> the same way.
> The {{Coder.bytesToLong()}} method should be modified to check for the first
> two characters being "-0" or "+" and throw a {{NumberFormatException}} if
> that is the case. Alternately, if there are places where we want to preserve
> the existing behaviour of {{Coder.bytesToLong()}}, an additional
> {{bytesToLongStrict()}} method could be added to the {{Coder}} class with
> this additional check.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9482) Radish commands do not match Redis error behaviour for integer arguments beginning "-0" and "+"
[
https://issues.apache.org/jira/browse/GEODE-9482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donal Evans updated GEODE-9482:
---
Summary: Radish commands do not match Redis error behaviour for integer
arguments beginning "-0" and "+" (was: Radish commands do not match Redis
error behaviour for integer arguments beginning "-0")
> Radish commands do not match Redis error behaviour for integer arguments
> beginning "-0" and "+"
> ---
>
> Key: GEODE-9482
> URL: https://issues.apache.org/jira/browse/GEODE-9482
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Priority: Major
>
> When using native Redis, commands that take integer arguments return {{"ERR
> value is not an integer or out of range"}} if the argument begins with "-0".
> The current implementation of these commands in Geode does not behave the
> same way.
> The {{Coder.bytesToLong()}} method should be modified to check for the first
> two characters being "-0" and throw a {{NumberFormatException}} if that is
> the case. Alternately, if there are places where we want to preserve the
> existing behaviour of {{Coder.bytesToLong()}}, an additional
> {{bytesToLongStrict()}} method could be added to the {{Coder}} class with
> this additional check.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9451) On demand authentication expiration and re-authentication
[ https://issues.apache.org/jira/browse/GEODE-9451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-9451: -- Labels: GeodeOperationAPI pull-request-available (was: GeodeOperationAPI) > On demand authentication expiration and re-authentication > - > > Key: GEODE-9451 > URL: https://issues.apache.org/jira/browse/GEODE-9451 > Project: Geode > Issue Type: New Feature > Components: core, security >Reporter: Jinmei Liao >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (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:all-tabpanel ] Xiaojian Zhou resolved GEODE-9496. -- Fix Version/s: 1.15.0 Assignee: Xiaojian Zhou Resolution: Fixed > 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 >Assignee: Xiaojian Zhou >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > 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] [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 ] ASF GitHub Bot updated GEODE-9458: -- Labels: GeodeOperationAPI pull-request-available (was: GeodeOperationAPI) > 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, pull-request-available > > 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-8719) CI Failure: org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest > givenServerCrashesDuringAPPEND_thenDataIsNotLost
[
https://issues.apache.org/jira/browse/GEODE-8719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donal Evans updated GEODE-8719:
---
Labels: flaky-test (was: )
> CI Failure:
> org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest >
> givenServerCrashesDuringAPPEND_thenDataIsNotLost
> -
>
> Key: GEODE-8719
> URL: https://issues.apache.org/jira/browse/GEODE-8719
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.14.0, 1.15.0
>Reporter: Sarah Abbey
>Assignee: Jens Deppe
>Priority: Minor
> Labels: flaky-test
>
> CI failure: https://concourse.apachegeode-ci.info/builds/207449
> {code:java}
> org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest >
> givenServerCrashesDuringAPPEND_thenDataIsNotLost FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.test.dunit.internal.IdentifiableCallable.call in VM 2
> running on Host e0e2f6af9445 with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:623)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:460)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:268)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:261)
> at
> org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest.startRedisVM(CrashAndNoRepeatDUnitTest.java:131)
> at
> org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest.givenServerCrashesDuringAPPEND_thenDataIsNotLost(CrashAndNoRepeatDUnitTest.java:164)
> Caused by:
> org.apache.geode.management.ManagementException: Could not start
> Redis Server using bind address: localhost/127.0.0.1 and port: 44579. Please
> make sure nothing else is running on this address/port combination.
> Caused by:
> java.net.BindException: Address already in use
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9319) CI failure: session.NativeRedisSessionExpirationAcceptanceTest > classMethod FAILED
[
https://issues.apache.org/jira/browse/GEODE-9319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donal Evans updated GEODE-9319:
---
Labels: flaky-test (was: )
> CI failure: session.NativeRedisSessionExpirationAcceptanceTest > classMethod
> FAILED
> ---
>
> Key: GEODE-9319
> URL: https://issues.apache.org/jira/browse/GEODE-9319
> Project: Geode
> Issue Type: Bug
> Components: redis
>Reporter: Jens Deppe
>Priority: Major
> Labels: flaky-test
>
> {noformat}
> session.NativeRedisSessionExpirationAcceptanceTest > classMethod FAILED
> 14:17:23java.lang.AssertionError: Suspicious strings were written to the
> log during this run.
> 14:17:23Fix the strings or use IgnoredException.addIgnoredException to
> ignore.
> 14:17:23
> ---
> 14:17:23Found suspect string in 'dunit_suspect-local.log' at line 287
> 14:17:23
> 14:17:23[error 2021/05/26 21:17:10.762 UTC tid=92]
> Failed to return response on inboundChannel
> 14:17:23io.netty.channel.StacklessClosedChannelException
> 14:17:23 at
> io.netty.channel.AbstractChannel$AbstractUnsafe.write(Object,
> ChannelPromise)(Unknown Source)
> 14:17:23at org.junit.Assert.fail(Assert.java:89)
> 14:17:23at
> org.apache.geode.test.dunit.internal.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:409)
> 14:17:23at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.after(ClusterStartupRule.java:185)
> 14:17:23at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.access$100(ClusterStartupRule.java:69)
> 14:17:23at
> org.apache.geode.test.dunit.rules.ClusterStartupRule$1.evaluate(ClusterStartupRule.java:140)
> 14:17:23at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> 14:17:23at
> org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> 14:17:23at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> 14:17:23at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110)
> 14:17:23at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
> 14:17:23at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
> 14:17:23at
> org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:62)
> 14:17:23at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
> 14:17:23at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 14:17:23at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 14:17:23at
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 14:17:23at java.lang.reflect.Method.invoke(Method.java:566)
> 14:17:23at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:36)
> 14:17:23at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> 14:17:23at
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:33)
> 14:17:23at
> org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:94)
> 14:17:23at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> 14:17:23at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:119)
> 14:17:23at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 14:17:23at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 14:17:23at
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 14:17:23at java.lang.reflect.Method.invoke(Method.java:566)
> 14:17:23at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:36)
> 14:17:23at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> 14:17:23at
> org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:182)
> 14:17:23at
> org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:164)
> 14:17:23at
> org.gradle.internal.remote.internal.hub.MessageHub$Handler.run(Messa
[jira] [Updated] (GEODE-9320) CI Failure: SetNXNativeRedisAcceptanceTest > classMethod FAILED
[
https://issues.apache.org/jira/browse/GEODE-9320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donal Evans updated GEODE-9320:
---
Labels: flaky-test (was: )
> CI Failure: SetNXNativeRedisAcceptanceTest > classMethod FAILED
> ---
>
> Key: GEODE-9320
> URL: https://issues.apache.org/jira/browse/GEODE-9320
> Project: Geode
> Issue Type: Bug
> Components: redis
>Reporter: Jens Deppe
>Priority: Major
> Labels: flaky-test
>
> {noformat}
> org.apache.geode.redis.internal.executor.string.SetNXNativeRedisAcceptanceTest
> > classMethod FAILED
> 13:40:47org.testcontainers.containers.ContainerLaunchException: Container
> startup failed
> 13:40:47at
> org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:330)
> 13:40:47at
> org.testcontainers.containers.GenericContainer.start(GenericContainer.java:311)
> 13:40:47at
> org.testcontainers.containers.DockerComposeContainer.startAmbassadorContainers(DockerComposeContainer.java:330)
> 13:40:47at
> org.testcontainers.containers.DockerComposeContainer.start(DockerComposeContainer.java:178)
> 13:40:47at
> org.apache.geode.redis.NativeRedisClusterTestRule$1.evaluate(NativeRedisClusterTestRule.java:85)
> 13:40:47at
> org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
> 13:40:47at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> 13:40:47at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> 13:40:47at
> org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> 13:40:47at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> 13:40:47at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110)
> 13:40:47at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
> 13:40:47at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
> 13:40:47at
> org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:62)
> 13:40:47at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
> 13:40:47at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 13:40:47at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 13:40:47at
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 13:40:47at java.lang.reflect.Method.invoke(Method.java:566)
> 13:40:47at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:36)
> 13:40:47at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> 13:40:47at
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:33)
> 13:40:47at
> org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:94)
> 13:40:47at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> 13:40:47at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:119)
> 13:40:47at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 13:40:47at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 13:40:47at
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 13:40:47at java.lang.reflect.Method.invoke(Method.java:566)
> 13:40:47at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:36)
> 13:40:47at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> 13:40:47at
> org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:182)
> 13:40:47at
> org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:164)
> 13:40:47at
> org.gradle.internal.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:414)
> 13:40:47at
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
> 13:40:47at
> org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48)
> 13:40:47at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.
[jira] [Updated] (GEODE-9506) CI Failure: BindException in SessionsAndCrashesDUnitTest
[
https://issues.apache.org/jira/browse/GEODE-9506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donal Evans updated GEODE-9506:
---
Labels: flaky-test (was: )
> CI Failure: BindException in SessionsAndCrashesDUnitTest
>
>
> Key: GEODE-9506
> URL: https://issues.apache.org/jira/browse/GEODE-9506
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Priority: Major
> Labels: flaky-test
>
> {noformat}
> org.apache.geode.redis.session.SessionsAndCrashesDUnitTest >
> sessionOperationsDoNotFail_whileServersAreRestarted FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.test.dunit.internal.IdentifiableCallable.call in VM 3
> running on Host
> heavy-lifter-48e50679-1ba5-54cd-8da2-5aadbb3287e4.c.apachegeode-ci.internal
> with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:461)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:270)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:262)
> at
> org.apache.geode.test.dunit.rules.RedisClusterStartupRule.startRedisVM(RedisClusterStartupRule.java:82)
> at
> org.apache.geode.redis.session.SessionsAndCrashesDUnitTest.startRedisVM(SessionsAndCrashesDUnitTest.java:93)
> at
> org.apache.geode.redis.session.SessionsAndCrashesDUnitTest.sessionOperationsDoNotFail_whileServersAreRestarted(SessionsAndCrashesDUnitTest.java:154)
> Caused by:
> org.apache.geode.management.ManagementException: Could not start
> server compatible with Redis using bind address: /127.0.0.1 and port: 35275.
> Please make sure nothing else is running on this address/port combination.
> at
> org.apache.geode.redis.internal.netty.NettyRedisServer.createBoundChannel(NettyRedisServer.java:222)
> at
> org.apache.geode.redis.internal.netty.NettyRedisServer.createChannel(NettyRedisServer.java:137)
> at
> org.apache.geode.redis.internal.netty.NettyRedisServer.(NettyRedisServer.java:116)
> at
> org.apache.geode.redis.internal.GeodeRedisServer.(GeodeRedisServer.java:94)
> at
> org.apache.geode.redis.internal.GeodeRedisService.startRedisServer(GeodeRedisService.java:112)
> at
> org.apache.geode.redis.internal.GeodeRedisService.handleEvent(GeodeRedisService.java:96)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.notifyResourceEventListeners(InternalDistributedSystem.java:2088)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.handleResourceEvent(InternalDistributedSystem.java:644)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1471)
> at
> org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:191)
> at
> org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:158)
> at
> org.apache.geode.cache.CacheFactory.create(CacheFactory.java:142)
> at
> org.apache.geode.test.junit.rules.ServerStarterRule.startServer(ServerStarterRule.java:204)
> at
> org.apache.geode.test.junit.rules.ServerStarterRule.before(ServerStarterRule.java:99)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.lambda$startServerVM$6d6c10c2$1(ClusterStartupRule.java:278)
> at
> org.apache.geode.test.dunit.internal.IdentifiableCallable.call(IdentifiableCallable.java:41)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.geode.test.dunit.internal.MethodInvoker.executeObject(MethodInvoker.java:123)
> at
> org.apache.geode.test.dunit.internal.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:78)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357)
> at sun.rmi.transport.Transport$1.run(Transport.java:200)
>
[jira] [Updated] (GEODE-9506) CI Failure: BindException in SessionsAndCrashesDUnitTest
[
https://issues.apache.org/jira/browse/GEODE-9506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donal Evans updated GEODE-9506:
---
Description:
{noformat}
org.apache.geode.redis.session.SessionsAndCrashesDUnitTest >
sessionOperationsDoNotFail_whileServersAreRestarted FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.test.dunit.internal.IdentifiableCallable.call in VM 3 running
on Host
heavy-lifter-48e50679-1ba5-54cd-8da2-5aadbb3287e4.c.apachegeode-ci.internal
with 4 VMs
at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
at org.apache.geode.test.dunit.VM.invoke(VM.java:461)
at
org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:270)
at
org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:262)
at
org.apache.geode.test.dunit.rules.RedisClusterStartupRule.startRedisVM(RedisClusterStartupRule.java:82)
at
org.apache.geode.redis.session.SessionsAndCrashesDUnitTest.startRedisVM(SessionsAndCrashesDUnitTest.java:93)
at
org.apache.geode.redis.session.SessionsAndCrashesDUnitTest.sessionOperationsDoNotFail_whileServersAreRestarted(SessionsAndCrashesDUnitTest.java:154)
Caused by:
org.apache.geode.management.ManagementException: Could not start server
compatible with Redis using bind address: /127.0.0.1 and port: 35275. Please
make sure nothing else is running on this address/port combination.
at
org.apache.geode.redis.internal.netty.NettyRedisServer.createBoundChannel(NettyRedisServer.java:222)
at
org.apache.geode.redis.internal.netty.NettyRedisServer.createChannel(NettyRedisServer.java:137)
at
org.apache.geode.redis.internal.netty.NettyRedisServer.(NettyRedisServer.java:116)
at
org.apache.geode.redis.internal.GeodeRedisServer.(GeodeRedisServer.java:94)
at
org.apache.geode.redis.internal.GeodeRedisService.startRedisServer(GeodeRedisService.java:112)
at
org.apache.geode.redis.internal.GeodeRedisService.handleEvent(GeodeRedisService.java:96)
at
org.apache.geode.distributed.internal.InternalDistributedSystem.notifyResourceEventListeners(InternalDistributedSystem.java:2088)
at
org.apache.geode.distributed.internal.InternalDistributedSystem.handleResourceEvent(InternalDistributedSystem.java:644)
at
org.apache.geode.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1471)
at
org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:191)
at
org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:158)
at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:142)
at
org.apache.geode.test.junit.rules.ServerStarterRule.startServer(ServerStarterRule.java:204)
at
org.apache.geode.test.junit.rules.ServerStarterRule.before(ServerStarterRule.java:99)
at
org.apache.geode.test.dunit.rules.ClusterStartupRule.lambda$startServerVM$6d6c10c2$1(ClusterStartupRule.java:278)
at
org.apache.geode.test.dunit.internal.IdentifiableCallable.call(IdentifiableCallable.java:41)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.apache.geode.test.dunit.internal.MethodInvoker.executeObject(MethodInvoker.java:123)
at
org.apache.geode.test.dunit.internal.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:78)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357)
at sun.rmi.transport.Transport$1.run(Transport.java:200)
at sun.rmi.transport.Transport$1.run(Transport.java:197)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
at
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:573)
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:834)
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:688)
at java.security.AccessController.doPrivileged(Native Method)
at
sun.rmi.tran
[jira] [Updated] (GEODE-9535) CI Failure: Tomcat7ClientServerTest > newContainersShouldShareDataAccess
[
https://issues.apache.org/jira/browse/GEODE-9535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donal Evans updated GEODE-9535:
---
Description:
{noformat}
> Task :geode-assembly:distributedTest
org.apache.geode.session.tests.Tomcat7ClientServerTest >
newContainersShouldShareDataAccess FAILED
java.lang.AssertionError: Suspicious strings were written to the log during
this run.
Fix the strings or use IgnoredException.addIgnoredException to ignore.
---
Found suspect string in 'dunit_suspect-vm0.log' at line 423
[fatal 2021/08/21 21:05:18.691 UTC tid=855]
Exception in processing request from 10.0.0.108
java.lang.Exception: Improperly configured client detected - use
addPoolLocator to configure its locators instead of addPoolServer.
at
org.apache.geode.distributed.internal.ProtocolCheckerImpl.checkProtocol(ProtocolCheckerImpl.java:31)
at
org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:342)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
---
Found suspect string in 'dunit_suspect-vm0.log' at line 540
[fatal 2021/08/21 21:05:30.875 UTC tid=855]
Exception in processing request from 10.0.0.108
java.lang.Exception: Improperly configured client detected - use
addPoolLocator to configure its locators instead of addPoolServer.
at
org.apache.geode.distributed.internal.ProtocolCheckerImpl.checkProtocol(ProtocolCheckerImpl.java:31)
at
org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:342)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
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.TestWatcher$1.evaluate(TestWatcher.java:61)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at
org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
at
org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:62)
at
org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:36)
at
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at
org.gradle.internal.dispatch.ContextClassLoaderDispat
[jira] [Updated] (GEODE-9428) CI Failure: PSetEXNativeRedisAcceptanceTest fails with CLUSTERDOWN error
[
https://issues.apache.org/jira/browse/GEODE-9428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donal Evans updated GEODE-9428:
---
Description:
*This ticket tracks failures seen in NativeRedisAcceptanceTests due to
non-Geode code. It is closed because no work will be done in the Geode project
to fix this issue. If the issue becomes unbearable, a bug should be opened with
Redis:
[https://github.com/redis/redis/issues|https://github.com/redis/redis/issues*]*
CI run is here:
[https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/acceptance-test-openjdk11/builds/82#L60e11384:311]
{code:java}
org.apache.geode.redis.internal.executor.string.PSetEXNativeRedisAcceptanceTest
> testPSetEX FAILED
redis.clients.jedis.exceptions.JedisClusterException: CLUSTERDOWN The
cluster is down
at redis.clients.jedis.Protocol.processError(Protocol.java:125)
at redis.clients.jedis.Protocol.process(Protocol.java:169)
at redis.clients.jedis.Protocol.read(Protocol.java:223)
at
redis.clients.jedis.Connection.readProtocolWithCheckingBroken(Connection.java:352)
at
redis.clients.jedis.Connection.getStatusCodeReply(Connection.java:270)
at redis.clients.jedis.Jedis.psetex(Jedis.java:3616)
at redis.clients.jedis.JedisCluster$30.execute(JedisCluster.java:572)
at redis.clients.jedis.JedisCluster$30.execute(JedisCluster.java:569)
at
redis.clients.jedis.JedisClusterCommand.runWithRetries(JedisClusterCommand.java:121)
at
redis.clients.jedis.JedisClusterCommand.run(JedisClusterCommand.java:45)
at redis.clients.jedis.JedisCluster.psetex(JedisCluster.java:574)
at
org.apache.geode.redis.internal.executor.string.AbstractPSetEXIntegrationTest.testPSetEX(AbstractPSetEXIntegrationTest.java:54)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:566)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at
org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
at
org.apache.geode.redis.NativeRedisClusterTestRule$1.evaluate(NativeRedisClusterTestRule.java:120)
at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
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.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
at
org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:62)
at
org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Delegating
[jira] [Resolved] (GEODE-9428) CI Failure: PSetEXNativeRedisAcceptanceTest fails with CLUSTERDOWN error
[
https://issues.apache.org/jira/browse/GEODE-9428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donal Evans resolved GEODE-9428.
Resolution: Invalid
> CI Failure: PSetEXNativeRedisAcceptanceTest fails with CLUSTERDOWN error
>
>
> Key: GEODE-9428
> URL: https://issues.apache.org/jira/browse/GEODE-9428
> Project: Geode
> Issue Type: Bug
> Components: redis
>Reporter: Hale Bales
>Priority: Major
>
> *This ticket tracks failures seen in NativeRedisAcceptanceTests due to
> non-Geode code. It is closed because no work will be done in the Geode
> project to fix this issue. If the issue becomes unbearable, a bug should be
> opened with Redis:
> [https://github.com/redis/redis/issues|https://github.com/redis/redis/issues*]*
> CI run is here:
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/acceptance-test-openjdk11/builds/82#L60e11384:311]
> {code:java}
> org.apache.geode.redis.internal.executor.string.PSetEXNativeRedisAcceptanceTest
> > testPSetEX FAILED
> redis.clients.jedis.exceptions.JedisClusterException: CLUSTERDOWN The
> cluster is down
> at redis.clients.jedis.Protocol.processError(Protocol.java:125)
> at redis.clients.jedis.Protocol.process(Protocol.java:169)
> at redis.clients.jedis.Protocol.read(Protocol.java:223)
> at
> redis.clients.jedis.Connection.readProtocolWithCheckingBroken(Connection.java:352)
> at
> redis.clients.jedis.Connection.getStatusCodeReply(Connection.java:270)
> at redis.clients.jedis.Jedis.psetex(Jedis.java:3616)
> at redis.clients.jedis.JedisCluster$30.execute(JedisCluster.java:572)
> at redis.clients.jedis.JedisCluster$30.execute(JedisCluster.java:569)
> at
> redis.clients.jedis.JedisClusterCommand.runWithRetries(JedisClusterCommand.java:121)
> at
> redis.clients.jedis.JedisClusterCommand.run(JedisClusterCommand.java:45)
> at redis.clients.jedis.JedisCluster.psetex(JedisCluster.java:574)
> at
> org.apache.geode.redis.internal.executor.string.AbstractPSetEXIntegrationTest.testPSetEX(AbstractPSetEXIntegrationTest.java:54)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at
> org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
> at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> at
> org.apache.geode.redis.NativeRedisClusterTestRule$1.evaluate(NativeRedisClusterTestRule.java:120)
> at
> org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> 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.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
>
[jira] [Updated] (GEODE-9506) CI Failure: BindException in SessionsAndCrashesDUnitTest
[
https://issues.apache.org/jira/browse/GEODE-9506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-9506:
--
Labels: flaky-test pull-request-available (was: flaky-test)
> CI Failure: BindException in SessionsAndCrashesDUnitTest
>
>
> Key: GEODE-9506
> URL: https://issues.apache.org/jira/browse/GEODE-9506
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Priority: Major
> Labels: flaky-test, pull-request-available
>
> {noformat}
> org.apache.geode.redis.session.SessionsAndCrashesDUnitTest >
> sessionOperationsDoNotFail_whileServersAreRestarted FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.test.dunit.internal.IdentifiableCallable.call in VM 3
> running on Host
> heavy-lifter-48e50679-1ba5-54cd-8da2-5aadbb3287e4.c.apachegeode-ci.internal
> with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:461)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:270)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:262)
> at
> org.apache.geode.test.dunit.rules.RedisClusterStartupRule.startRedisVM(RedisClusterStartupRule.java:82)
> at
> org.apache.geode.redis.session.SessionsAndCrashesDUnitTest.startRedisVM(SessionsAndCrashesDUnitTest.java:93)
> at
> org.apache.geode.redis.session.SessionsAndCrashesDUnitTest.sessionOperationsDoNotFail_whileServersAreRestarted(SessionsAndCrashesDUnitTest.java:154)
> Caused by:
> org.apache.geode.management.ManagementException: Could not start
> server compatible with Redis using bind address: /127.0.0.1 and port: 35275.
> Please make sure nothing else is running on this address/port combination.
> at
> org.apache.geode.redis.internal.netty.NettyRedisServer.createBoundChannel(NettyRedisServer.java:222)
> at
> org.apache.geode.redis.internal.netty.NettyRedisServer.createChannel(NettyRedisServer.java:137)
> at
> org.apache.geode.redis.internal.netty.NettyRedisServer.(NettyRedisServer.java:116)
> at
> org.apache.geode.redis.internal.GeodeRedisServer.(GeodeRedisServer.java:94)
> at
> org.apache.geode.redis.internal.GeodeRedisService.startRedisServer(GeodeRedisService.java:112)
> at
> org.apache.geode.redis.internal.GeodeRedisService.handleEvent(GeodeRedisService.java:96)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.notifyResourceEventListeners(InternalDistributedSystem.java:2088)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.handleResourceEvent(InternalDistributedSystem.java:644)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1471)
> at
> org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:191)
> at
> org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:158)
> at
> org.apache.geode.cache.CacheFactory.create(CacheFactory.java:142)
> at
> org.apache.geode.test.junit.rules.ServerStarterRule.startServer(ServerStarterRule.java:204)
> at
> org.apache.geode.test.junit.rules.ServerStarterRule.before(ServerStarterRule.java:99)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.lambda$startServerVM$6d6c10c2$1(ClusterStartupRule.java:278)
> at
> org.apache.geode.test.dunit.internal.IdentifiableCallable.call(IdentifiableCallable.java:41)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.geode.test.dunit.internal.MethodInvoker.executeObject(MethodInvoker.java:123)
> at
> org.apache.geode.test.dunit.internal.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:78)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357)
>
[jira] [Updated] (GEODE-9442) CI Failure: acceptance-test-openjdk8 timed out
[ https://issues.apache.org/jira/browse/GEODE-9442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-9442: -- Labels: pull-request-available (was: ) > CI Failure: acceptance-test-openjdk8 timed out > -- > > Key: GEODE-9442 > URL: https://issues.apache.org/jira/browse/GEODE-9442 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Eric Shu >Priority: Major > Labels: pull-request-available > > This acceptance-test-openjdk8 failed due to timeout. > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/acceptance-test-openjdk8/builds/88 > It does not appear to be one particular test hang -- as all running tests are > finished showing status of SUCCESS. > There are 1153 tests shown being run in this run. > Test Summary > 1153 > tests > The previous run showed 1295 tests were run. > Test Summary > 1295 > tests > However, it shows that gradle no able to shut down one test worker: > in daemon-4088.out.log under .gradle_logs directory following exception was > seen: > Daemon is stopping immediately stop command received > Daemon vm is shutting down... The daemon has exited normally or was > terminated in response to a user interrupt. > failed to abort Gradle Test Executor 143 > org.gradle.process.internal.ExecException: A problem occurred waiting for > process 'Gradle Test Executor 143' to complete. > at > org.gradle.process.internal.DefaultExecHandle.execExceptionFor(DefaultExecHandle.java:241) > at > org.gradle.process.internal.DefaultExecHandle.setEndStateInfo(DefaultExecHandle.java:218) > at > org.gradle.process.internal.DefaultExecHandle.failed(DefaultExecHandle.java:369) > at > org.gradle.process.internal.ExecHandleRunner.run(ExecHandleRunner.java:87) > at > org.gradle.internal.operations.CurrentBuildOperationPreservingRunnable.run(CurrentBuildOperationPreservingRunnable.java:42) > at > org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64) > at > org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at > org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:56) > at java.lang.Thread.run(Thread.java:748) > Caused by: java.lang.IllegalStateException: Shutdown in progress > at > java.lang.ApplicationShutdownHooks.remove(ApplicationShutdownHooks.java:82) > at java.lang.Runtime.removeShutdownHook(Runtime.java:239) > at > org.gradle.process.internal.shutdown.ShutdownHooks.removeShutdownHook(ShutdownHooks.java:33) > at > org.gradle.process.internal.DefaultExecHandle.setEndStateInfo(DefaultExecHandle.java:208) > at > org.gradle.process.internal.DefaultExecHandle.aborted(DefaultExecHandle.java:365) > at > org.gradle.process.internal.ExecHandleRunner.completed(ExecHandleRunner.java:108) > at > org.gradle.process.internal.ExecHandleRunner.run(ExecHandleRunner.java:84) > ... 7 more > Also, in > geode-apis-compatible-with-redis/build/test-results/acceptanceTest/binary > output.bin file that Redis container was started but no further information > for its shutdown. No sure if this is normal or not. > ^A<9c>^H^@<8a>^A[info 2021/07/20 16:55:00.011 UTC tid=0xa] > Ryuk started - will monitor and terminate Testcontainers containers on JVM > exit > ^A<9c>^H^@^A > ^A<9c>^H^@Q[info 2021/07/20 16:55:00.012 UTC tid=0xa] Checking > the system... > ^A<9c>^H^@^A > ^A<9c>^H^@p[info 2021/07/20 16:55:00.013 UTC tid=0xa] > â<9c><94>ï¸<8e> Docker server version should be at least 1.6.0 > ^A<9c>^H^@^A > ^A<9c>^H^@~[info 2021/07/20 16:55:00.142 UTC tid=0xa] > â<9c><94>ï¸<8e> Docker environment should have more than 2GB free disk space > ^A<9c>^H^@^A > ^A<9c>^H^@d[info 2021/07/20 16:55:00.161 UTC tid=0xa] Creating > container for image: redis:5.0.6 > ^A<9c>^H^@^A > ^A<9c>^H^@<97>^A[info 2021/07/20 16:55:00.218 UTC tid=0xa] > Starting container with ID: > 3d1530c27f0b4f6e526bfc48b8232708abd3e0de55f188c74e007db30a19d634 > ^A<9c>^H^@^A > ^A<9c>^H^@<9e>^A[info 2021/07/20 16:55:00.658 UTC tid=0xa] > Container redis:5.0.6 is starting: > 3d1530c27f0b4f6e526bfc48b8232708abd3e0de55f188c74e007db30a19d634 > ^A<9c>^H^@^A > ^A<9c>^H^@d[info 2021/07/20 16:55:00.789 UTC tid=0xa] > Container redis:5.0.6 started in PT0.644S > ^A<9c>^H^@^A > ^A<9c>^H^@r[info 2021/07/20 16:55:00.791 UTC tid=0xa] Started > redis container with exposed port 6379 -> 33290 > Someone has more knowledge of redis
[jira] [Assigned] (GEODE-9528) CI Failure: DistributionAdvisorIntegrationTest > verifyMembershipListenerIsRemovedAfterForceDisconnect
[
https://issues.apache.org/jira/browse/GEODE-9528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ernest Burghardt reassigned GEODE-9528:
---
Assignee: Ernest Burghardt
> 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
>Assignee: Ernest Burghardt
>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-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:comment-tabpanel&focusedCommentId=17403396#comment-17403396
]
ASF subversion and git services commented on GEODE-9515:
Commit 280bd841427f244f507633826def2f845a9b10ef in geode's branch
refs/heads/develop from Jianxia Chen
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=280bd84 ]
GEODE-9515: Skip setting MBeanServer when JMXConnectorServer will set it (#6770)
> 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-9442) CI Failure: acceptance-test-openjdk8 timed out
[ https://issues.apache.org/jira/browse/GEODE-9442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17403398#comment-17403398 ] Donal Evans commented on GEODE-9442: The logging for the Redis component of this ticket is normal, so this issue is purely a gradle problem. Additional logging will be added to make it clear when the Redis container is stopping and this ticket will be closed. > CI Failure: acceptance-test-openjdk8 timed out > -- > > Key: GEODE-9442 > URL: https://issues.apache.org/jira/browse/GEODE-9442 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Eric Shu >Priority: Major > Labels: pull-request-available > > This acceptance-test-openjdk8 failed due to timeout. > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/acceptance-test-openjdk8/builds/88 > It does not appear to be one particular test hang -- as all running tests are > finished showing status of SUCCESS. > There are 1153 tests shown being run in this run. > Test Summary > 1153 > tests > The previous run showed 1295 tests were run. > Test Summary > 1295 > tests > However, it shows that gradle no able to shut down one test worker: > in daemon-4088.out.log under .gradle_logs directory following exception was > seen: > Daemon is stopping immediately stop command received > Daemon vm is shutting down... The daemon has exited normally or was > terminated in response to a user interrupt. > failed to abort Gradle Test Executor 143 > org.gradle.process.internal.ExecException: A problem occurred waiting for > process 'Gradle Test Executor 143' to complete. > at > org.gradle.process.internal.DefaultExecHandle.execExceptionFor(DefaultExecHandle.java:241) > at > org.gradle.process.internal.DefaultExecHandle.setEndStateInfo(DefaultExecHandle.java:218) > at > org.gradle.process.internal.DefaultExecHandle.failed(DefaultExecHandle.java:369) > at > org.gradle.process.internal.ExecHandleRunner.run(ExecHandleRunner.java:87) > at > org.gradle.internal.operations.CurrentBuildOperationPreservingRunnable.run(CurrentBuildOperationPreservingRunnable.java:42) > at > org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64) > at > org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at > org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:56) > at java.lang.Thread.run(Thread.java:748) > Caused by: java.lang.IllegalStateException: Shutdown in progress > at > java.lang.ApplicationShutdownHooks.remove(ApplicationShutdownHooks.java:82) > at java.lang.Runtime.removeShutdownHook(Runtime.java:239) > at > org.gradle.process.internal.shutdown.ShutdownHooks.removeShutdownHook(ShutdownHooks.java:33) > at > org.gradle.process.internal.DefaultExecHandle.setEndStateInfo(DefaultExecHandle.java:208) > at > org.gradle.process.internal.DefaultExecHandle.aborted(DefaultExecHandle.java:365) > at > org.gradle.process.internal.ExecHandleRunner.completed(ExecHandleRunner.java:108) > at > org.gradle.process.internal.ExecHandleRunner.run(ExecHandleRunner.java:84) > ... 7 more > Also, in > geode-apis-compatible-with-redis/build/test-results/acceptanceTest/binary > output.bin file that Redis container was started but no further information > for its shutdown. No sure if this is normal or not. > ^A<9c>^H^@<8a>^A[info 2021/07/20 16:55:00.011 UTC tid=0xa] > Ryuk started - will monitor and terminate Testcontainers containers on JVM > exit > ^A<9c>^H^@^A > ^A<9c>^H^@Q[info 2021/07/20 16:55:00.012 UTC tid=0xa] Checking > the system... > ^A<9c>^H^@^A > ^A<9c>^H^@p[info 2021/07/20 16:55:00.013 UTC tid=0xa] > â<9c><94>ï¸<8e> Docker server version should be at least 1.6.0 > ^A<9c>^H^@^A > ^A<9c>^H^@~[info 2021/07/20 16:55:00.142 UTC tid=0xa] > â<9c><94>ï¸<8e> Docker environment should have more than 2GB free disk space > ^A<9c>^H^@^A > ^A<9c>^H^@d[info 2021/07/20 16:55:00.161 UTC tid=0xa] Creating > container for image: redis:5.0.6 > ^A<9c>^H^@^A > ^A<9c>^H^@<97>^A[info 2021/07/20 16:55:00.218 UTC tid=0xa] > Starting container with ID: > 3d1530c27f0b4f6e526bfc48b8232708abd3e0de55f188c74e007db30a19d634 > ^A<9c>^H^@^A > ^A<9c>^H^@<9e>^A[info 2021/07/20 16:55:00.658 UTC tid=0xa] > Container redis:5.0.6 is starting: > 3d1530c27f0b4f6e526bfc48b8232708abd3e0de55f188c74e007db30a19d634 > ^A<9c>^H^@^A > ^A<9c>^H^@d[info 2021/07/20 16:55:00.
[jira] [Created] (GEODE-9537) CqDataUsingPoolDUnitTest (and CqDataUsingPoolOptimizedExecuteDUnitTest) should not use ephemeral ports
Jens Deppe created GEODE-9537:
-
Summary: CqDataUsingPoolDUnitTest (and
CqDataUsingPoolOptimizedExecuteDUnitTest) should not use ephemeral ports
Key: GEODE-9537
URL: https://issues.apache.org/jira/browse/GEODE-9537
Project: Geode
Issue Type: Test
Components: tests
Reporter: Jens Deppe
These tests currently use ephemeral ports for components that are stopped and
restarted during the test. It can happen that other, concurrently running
tests, will start using these same ports causing test failures (but not in the
tests mentioned here).
Test failures appear as dunit suspect strings:
{noformat}
java.lang.AssertionError: Suspicious strings were written to the log during
this run.
Fix the strings or use IgnoredException.addIgnoredException to ignore.
---
Found suspect string in 'dunit_suspect-locator.log' at line 347
[fatal 2021/08/21 19:46:08.527 UTC tid=47]
Exception in processing request from 10.0.0.107
java.lang.Exception: Improperly configured client detected - use
addPoolLocator to configure its locators instead of addPoolServer.
at
org.apache.geode.distributed.internal.ProtocolCheckerImpl.checkProtocol(ProtocolCheckerImpl.java:31)
at
org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:342)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9537) CqDataUsingPoolDUnitTest (and CqDataUsingPoolOptimizedExecuteDUnitTest) should not use ephemeral ports
[
https://issues.apache.org/jira/browse/GEODE-9537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17403410#comment-17403410
]
Geode Integration commented on GEODE-9537:
--
Seen in [distributed-test-openjdk8
#1386|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/1386]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0426/test-results/distributedTest/1629582428/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0426/test-artifacts/1629582428/distributedtestfiles-openjdk8-1.15.0-build.0426.tgz].
> CqDataUsingPoolDUnitTest (and CqDataUsingPoolOptimizedExecuteDUnitTest)
> should not use ephemeral ports
> --
>
> Key: GEODE-9537
> URL: https://issues.apache.org/jira/browse/GEODE-9537
> Project: Geode
> Issue Type: Test
> Components: tests
>Reporter: Jens Deppe
>Priority: Major
>
> These tests currently use ephemeral ports for components that are stopped and
> restarted during the test. It can happen that other, concurrently running
> tests, will start using these same ports causing test failures (but not in
> the tests mentioned here).
> Test failures appear as dunit suspect strings:
> {noformat}
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in 'dunit_suspect-locator.log' at line 347
> [fatal 2021/08/21 19:46:08.527 UTC tid=47]
> Exception in processing request from 10.0.0.107
> java.lang.Exception: Improperly configured client detected - use
> addPoolLocator to configure its locators instead of addPoolServer.
> at
> org.apache.geode.distributed.internal.ProtocolCheckerImpl.checkProtocol(ProtocolCheckerImpl.java:31)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:342)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-9537) CqDataUsingPoolDUnitTest (and CqDataUsingPoolOptimizedExecuteDUnitTest) should not use ephemeral ports
[
https://issues.apache.org/jira/browse/GEODE-9537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jens Deppe reassigned GEODE-9537:
-
Assignee: Jens Deppe
> CqDataUsingPoolDUnitTest (and CqDataUsingPoolOptimizedExecuteDUnitTest)
> should not use ephemeral ports
> --
>
> Key: GEODE-9537
> URL: https://issues.apache.org/jira/browse/GEODE-9537
> Project: Geode
> Issue Type: Test
> Components: tests
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
>
> These tests currently use ephemeral ports for components that are stopped and
> restarted during the test. It can happen that other, concurrently running
> tests, will start using these same ports causing test failures (but not in
> the tests mentioned here).
> Test failures appear as dunit suspect strings:
> {noformat}
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in 'dunit_suspect-locator.log' at line 347
> [fatal 2021/08/21 19:46:08.527 UTC tid=47]
> Exception in processing request from 10.0.0.107
> java.lang.Exception: Improperly configured client detected - use
> addPoolLocator to configure its locators instead of addPoolServer.
> at
> org.apache.geode.distributed.internal.ProtocolCheckerImpl.checkProtocol(ProtocolCheckerImpl.java:31)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:342)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9537) CqDataUsingPoolDUnitTest (and CqDataUsingPoolOptimizedExecuteDUnitTest) should not use ephemeral ports
[
https://issues.apache.org/jira/browse/GEODE-9537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17403411#comment-17403411
]
Geode Integration commented on GEODE-9537:
--
Seen in [distributed-test-openjdk8
#1382|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/1382]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0426/test-results/distributedTest/1629580178/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0426/test-artifacts/1629580178/distributedtestfiles-openjdk8-1.15.0-build.0426.tgz].
> CqDataUsingPoolDUnitTest (and CqDataUsingPoolOptimizedExecuteDUnitTest)
> should not use ephemeral ports
> --
>
> Key: GEODE-9537
> URL: https://issues.apache.org/jira/browse/GEODE-9537
> Project: Geode
> Issue Type: Test
> Components: tests
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
>
> These tests currently use ephemeral ports for components that are stopped and
> restarted during the test. It can happen that other, concurrently running
> tests, will start using these same ports causing test failures (but not in
> the tests mentioned here).
> Test failures appear as dunit suspect strings:
> {noformat}
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in 'dunit_suspect-locator.log' at line 347
> [fatal 2021/08/21 19:46:08.527 UTC tid=47]
> Exception in processing request from 10.0.0.107
> java.lang.Exception: Improperly configured client detected - use
> addPoolLocator to configure its locators instead of addPoolServer.
> at
> org.apache.geode.distributed.internal.ProtocolCheckerImpl.checkProtocol(ProtocolCheckerImpl.java:31)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:342)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian Jira
(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=17403412#comment-17403412
]
ASF subversion and git services commented on GEODE-9071:
Commit ce6b1280ba57fbdbd1bb52104f71516288635257 in geode's branch
refs/heads/support/1.14 from Eric Shu
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=ce6b128 ]
GEODE-9071: Add wait before check cq listener invocations. (#6785)
* Cq events sent to client asynchronously. Need to wait events are
all delivered.
(cherry picked from commit 018fb585b1750a3186ad4693744ed5630d869182)
> 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
>Assignee: Eric Shu
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
>
> {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] [Updated] (GEODE-9071) CI Failure: PartitionedRegionCqQueryDUnitTest > testRemoveAllWithCQLocalDestroy
[
https://issues.apache.org/jira/browse/GEODE-9071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Shu updated GEODE-9071:
Labels: GeodeOperationAPI blocks-1.12.5 blocks-1.13.5 blocks-1.14.0
pull-request-available (was: GeodeOperationAPI pull-request-available)
> 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
>Assignee: Eric Shu
>Priority: Major
> Labels: GeodeOperationAPI, blocks-1.12.5, blocks-1.13.5,
> blocks-1.14.0, pull-request-available
>
> {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-9071) CI Failure: PartitionedRegionCqQueryDUnitTest > testRemoveAllWithCQLocalDestroy
[
https://issues.apache.org/jira/browse/GEODE-9071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17403419#comment-17403419
]
ASF subversion and git services commented on GEODE-9071:
Commit a1cd4ea85a08138df497045fb31d23510631daae in geode's branch
refs/heads/support/1.13 from Eric Shu
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=a1cd4ea ]
GEODE-9071: Add wait before check cq listener invocations. (#6785)
* Cq events sent to client asynchronously. Need to wait events are
all delivered.
(cherry picked from commit 018fb585b1750a3186ad4693744ed5630d869182)
> 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
>Assignee: Eric Shu
>Priority: Major
> Labels: GeodeOperationAPI, blocks-1.12.5, blocks-1.13.5,
> blocks-1.14.0, pull-request-available
>
> {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-9071) CI Failure: PartitionedRegionCqQueryDUnitTest > testRemoveAllWithCQLocalDestroy
[
https://issues.apache.org/jira/browse/GEODE-9071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17403423#comment-17403423
]
ASF subversion and git services commented on GEODE-9071:
Commit f938c4a0dd136d9c923b182b9f853f8153e024c0 in geode's branch
refs/heads/support/1.12 from Eric Shu
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=f938c4a ]
GEODE-9071: Add wait before check cq listener invocations. (#6785)
* Cq events sent to client asynchronously. Need to wait events are
all delivered.
(cherry picked from commit 018fb585b1750a3186ad4693744ed5630d869182)
> 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
>Assignee: Eric Shu
>Priority: Major
> Labels: GeodeOperationAPI, blocks-1.12.5, blocks-1.13.5,
> blocks-1.14.0, pull-request-available
>
> {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] [Resolved] (GEODE-9071) CI Failure: PartitionedRegionCqQueryDUnitTest > testRemoveAllWithCQLocalDestroy
[
https://issues.apache.org/jira/browse/GEODE-9071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Shu resolved GEODE-9071.
-
Resolution: Fixed
> 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
>Assignee: Eric Shu
>Priority: Major
> Labels: GeodeOperationAPI, blocks-1.12.5, blocks-1.13.5,
> blocks-1.14.0, pull-request-available
>
> {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-9241) CI failure in PartitionedRegionCqQueryDUnitTest > testPutAllWithCQLocalDestroy
[
https://issues.apache.org/jira/browse/GEODE-9241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17403425#comment-17403425
]
Eric Shu commented on GEODE-9241:
-
Fixed with GEODE-9071 check-in.
> CI failure in PartitionedRegionCqQueryDUnitTest > testPutAllWithCQLocalDestroy
> --
>
> Key: GEODE-9241
> URL: https://issues.apache.org/jira/browse/GEODE-9241
> Project: Geode
> Issue Type: Bug
> Components: cq
>Affects Versions: 1.15.0
>Reporter: Ray Ingles
>Assignee: Eric Shu
>Priority: Major
> Labels: GeodeOperationAPI, release-blocker
>
> CI failure seen here:
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/213]
> Stack trace as follows:
>
> {code:java}
> > Task :geode-cq:distributedTest
> org.apache.geode.cache.query.cq.dunit.PartitionedRegionCqQueryDUnitTest >
> testPutAllWithCQLocalDestroy FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache.query.cq.dunit.PartitionedRegionCqQueryDUnitTest$$Lambda$82/1306882276.run
> in VM 2 running on Host cae68a7c0ae3 with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:448)
> at
> org.apache.geode.cache.query.cq.dunit.PartitionedRegionCqQueryDUnitTest.testPutAllWithCQLocalDestroy(PartitionedRegionCqQueryDUnitTest.java:178)
> Caused by:
> org.junit.ComparisonFailure: expected:<9[99]> but was:<9[75]>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.cache.query.cq.dunit.PartitionedRegionCqQueryDUnitTest.lambda$testPutAllWithCQLocalDestroy$c93719d5$3(PartitionedRegionCqQueryDUnitTest.java:186)
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-9241) CI failure in PartitionedRegionCqQueryDUnitTest > testPutAllWithCQLocalDestroy
[
https://issues.apache.org/jira/browse/GEODE-9241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Shu resolved GEODE-9241.
-
Fix Version/s: 1.15.0
1.14.0
1.13.5
1.12.5
Resolution: Fixed
> CI failure in PartitionedRegionCqQueryDUnitTest > testPutAllWithCQLocalDestroy
> --
>
> Key: GEODE-9241
> URL: https://issues.apache.org/jira/browse/GEODE-9241
> Project: Geode
> Issue Type: Bug
> Components: cq
>Affects Versions: 1.15.0
>Reporter: Ray Ingles
>Assignee: Eric Shu
>Priority: Major
> Labels: GeodeOperationAPI, release-blocker
> Fix For: 1.12.5, 1.13.5, 1.14.0, 1.15.0
>
>
> CI failure seen here:
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/213]
> Stack trace as follows:
>
> {code:java}
> > Task :geode-cq:distributedTest
> org.apache.geode.cache.query.cq.dunit.PartitionedRegionCqQueryDUnitTest >
> testPutAllWithCQLocalDestroy FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache.query.cq.dunit.PartitionedRegionCqQueryDUnitTest$$Lambda$82/1306882276.run
> in VM 2 running on Host cae68a7c0ae3 with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:448)
> at
> org.apache.geode.cache.query.cq.dunit.PartitionedRegionCqQueryDUnitTest.testPutAllWithCQLocalDestroy(PartitionedRegionCqQueryDUnitTest.java:178)
> Caused by:
> org.junit.ComparisonFailure: expected:<9[99]> but was:<9[75]>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.cache.query.cq.dunit.PartitionedRegionCqQueryDUnitTest.lambda$testPutAllWithCQLocalDestroy$c93719d5$3(PartitionedRegionCqQueryDUnitTest.java:186)
> {code}
>
--
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
]
Alexander Murmann updated GEODE-9527:
-
Labels: pull-request-available (was: blocks-1.12.5 blocks-1.13.5
blocks-1.14.0 pull-request-available)
> 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
>Assignee: Ernest Burghardt
>Priority: Major
> Labels: pull-request-available
>
> 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=17403426#comment-17403426
]
Alexander Murmann commented on GEODE-9527:
--
I removed the release blocker labels, as this is ProtoBuf related which is
experimental
> 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
>Assignee: Ernest Burghardt
>Priority: Major
> Labels: pull-request-available
>
> 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-9071) CI Failure: PartitionedRegionCqQueryDUnitTest > testRemoveAllWithCQLocalDestroy
[
https://issues.apache.org/jira/browse/GEODE-9071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Shu updated GEODE-9071:
Fix Version/s: 1.15.0
1.14.0
1.13.5
1.12.5
> 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
>Assignee: Eric Shu
>Priority: Major
> Labels: GeodeOperationAPI, blocks-1.12.5, blocks-1.13.5,
> blocks-1.14.0, pull-request-available
> Fix For: 1.12.5, 1.13.5, 1.14.0, 1.15.0
>
>
> {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-9528) CI Failure: DistributionAdvisorIntegrationTest > verifyMembershipListenerIsRemovedAfterForceDisconnect
[
https://issues.apache.org/jira/browse/GEODE-9528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17403449#comment-17403449
]
Geode Integration commented on GEODE-9528:
--
Seen on support/1.12 in [integration-test-openjdk11
#35|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/integration-test-openjdk11/builds/35]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0273/test-results/integrationTest/1629762661/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0273/test-artifacts/1629762661/integrationtestfiles-openjdk11-1.12.5-build.0273.tgz].
> CI Failure: DistributionAdvisorIntegrationTest >
> verifyMembershipListenerIsRemovedAfterForceDisconnect
> --
>
> Key: GEODE-9528
> URL: https://issues.apache.org/jira/browse/GEODE-9528
> Project: Geode
> Issue Type: Bug
> Components: membership
>Affects Versions: 1.12.5, 1.13.5, 1.14.0
>Reporter: Owen Nichols
>Assignee: Ernest Burghardt
>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-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=17403451#comment-17403451
]
Geode Integration commented on GEODE-7702:
--
Seen on support/1.12 in [distributed-test-openjdk8
#29|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/distributed-test-openjdk8/builds/29]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0273/test-results/distributedTest/1629769334/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0273/test-artifacts/1629769334/distributedtestfiles-openjdk8-1.12.5-build.0273.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)
