[jira] [Updated] (GEODE-9529) fix release scripts

2021-08-20 Thread ASF GitHub Bot (Jira)


 [ 
https://issues.apache.org/jira/browse/GEODE-9529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated GEODE-9529:
--
Labels: pull-request-available  (was: )

> 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
>
> * update benchmark baseline on support branch on new minor release
> * change end-of-support message to version-based not time-based
> * remind to post to GitHub



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


[jira] [Updated] (GEODE-9529) fix release scripts

2021-08-20 Thread Owen Nichols (Jira)


 [ 
https://issues.apache.org/jira/browse/GEODE-9529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Owen Nichols updated GEODE-9529:

Description: 
* 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

  was:
* update benchmark baseline on support branch on new minor release

* change end-of-support message to version-based not time-based

* remind to post to GitHub


> 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
>
> * 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-7702) DistributedAckRegionCCEDUnitTest > testClearOnNonReplicateWithConcurrentEvents is showing a product bug

2021-08-20 Thread Geode Integration (Jira)


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

Geode Integration commented on GEODE-7702:
--

Seen on support/1.12 in [distributed-test-openjdk8 
#27|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/distributed-test-openjdk8/builds/27]
 ... see [test 
results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0272/test-results/distributedTest/1629455888/]
 or download 
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.5-build.0272/test-artifacts/1629455888/distributedtestfiles-openjdk8-1.12.5-build.0272.tgz].

> DistributedAckRegionCCEDUnitTest > 
> testClearOnNonReplicateWithConcurrentEvents is showing a product bug
> ---
>
> Key: GEODE-7702
> URL: https://issues.apache.org/jira/browse/GEODE-7702
> Project: Geode
>  Issue Type: Bug
>  Components: client/server
>Reporter: Mark Hanson
>Assignee: Xiaojian Zhou
>Priority: Major
>  Labels: GeodeCommons
> Fix For: 1.14.0
>
>
> testClearOnNonReplicateWithConcurrentEvents in 
> DistributedAckRegionCCEDUnitTest.java
> versionTestClearOnNonReplicateWithConcurrentEvents in 
> MultiVMRegionTestCase.java 
> doOpsLoop
> doOpsLoopNoFlush
> {noformat}
> case 5:
>   if (includeClear) {
> CCRegion.clear();
> break;
>   } else {
> if (CCRegion.getAttributes().getDataPolicy().withReplication()) {
>   if (oldkey != null) {
> CCRegion.putIfAbsent(oldkey, value);
>   }
>   break;
> } // else fall through to invalidate
>   } {noformat}
> the addition of this chunk of code causes this test to fail.
> The core of the problem is that a putall and a clear are happening 
> concurrently and the "system" does not respond by either clearing all entries 
> or letting all entries persist.



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


[jira] [Commented] (GEODE-9525) Add Radish benchmark tests to CI

2021-08-20 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on GEODE-9525:


Commit 9fcbb743cfdd57bff1ba40b10639e769148b5cc3 in geode's branch 
refs/heads/develop 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] [Updated] (GEODE-5703) CI Failure: GemFireConfigException

2021-08-20 Thread Donal Evans (Jira)


 [ 
https://issues.apache.org/jira/browse/GEODE-5703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donal Evans updated GEODE-5703:
---
Summary: CI Failure: GemFireConfigException  (was: CI Failure: 
AlterRuntimeCommandDUnitTest > 
alterStatArchiveFileWithMember_updatesSelectedServerConfigs(true))

> CI Failure: GemFireConfigException
> --
>
> Key: GEODE-5703
> URL: https://issues.apache.org/jira/browse/GEODE-5703
> Project: Geode
>  Issue Type: Bug
>Reporter: Hale Bales
>Priority: Major
>  Labels: swat
> Attachments: TestResultsPage.htm
>
>
> CI Failure can be found here:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/363
> Failed with Stack Trace:
> {code:java}
> org.apache.geode.management.internal.cli.commands.AlterRuntimeCommandDUnitTest
>  > alterStatArchiveFileWithMember_updatesSelectedServerConfigs(true) [0] 
> FAILED
>   
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.test.dunit.rules.ClusterStartupRule$$Lambda$41/1318057984.call
>  in VM 0 running on Host fca019e1fb13 with 4 VMs
>   
> at org.apache.geode.test.dunit.VM.invoke(VM.java:450)
>   
> at org.apache.geode.test.dunit.VM.invoke(VM.java:419)
>   
> at org.apache.geode.test.dunit.VM.invoke(VM.java:385)
>   
> at 
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startLocatorVM(ClusterStartupRule.java:198)
>   
> at 
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startLocatorVM(ClusterStartupRule.java:191)
>   
> at 
> org.apache.geode.management.internal.cli.commands.AlterRuntimeCommandDUnitTest.alterStatArchiveFileWithMember_updatesSelectedServerConfigs(AlterRuntimeCommandDUnitTest.java:466)
>   
>   
> Caused by:
>   
> org.apache.geode.GemFireConfigException: Unable to join the 
> distributed system.  Operation either timed out, was stopped or Locator does 
> not exist.
> {code}



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


[jira] [Commented] (GEODE-5703) CI Failure: GemFireConfigException in GMSMembershipManager.join() when trying to create Cache

2021-08-20 Thread Geode Integration (Jira)


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

Geode Integration commented on GEODE-5703:
--

Seen on support/1.14 in [UpgradeTestOpenJDK8 
#66|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/UpgradeTestOpenJDK8/builds/66]
 ... see [test 
results|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0770/test-results/upgradeTest/1619235491/]
 or download 
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0770/test-artifacts/1619235491/upgradetestfiles-OpenJDK8-1.14.0-build.0770.tgz].

> CI Failure: GemFireConfigException in GMSMembershipManager.join() when trying 
> to create Cache
> -
>
> Key: GEODE-5703
> URL: https://issues.apache.org/jira/browse/GEODE-5703
> Project: Geode
>  Issue Type: Bug
>Reporter: Hale Bales
>Priority: Major
>  Labels: swat
> Attachments: TestResultsPage.htm
>
>
> CI Failure can be found here:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/363
> Failed with Stack Trace:
> {code:java}
> org.apache.geode.management.internal.cli.commands.AlterRuntimeCommandDUnitTest
>  > alterStatArchiveFileWithMember_updatesSelectedServerConfigs(true) [0] 
> FAILED
>   
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.test.dunit.rules.ClusterStartupRule$$Lambda$41/1318057984.call
>  in VM 0 running on Host fca019e1fb13 with 4 VMs
>   
> at org.apache.geode.test.dunit.VM.invoke(VM.java:450)
>   
> at org.apache.geode.test.dunit.VM.invoke(VM.java:419)
>   
> at org.apache.geode.test.dunit.VM.invoke(VM.java:385)
>   
> at 
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startLocatorVM(ClusterStartupRule.java:198)
>   
> at 
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startLocatorVM(ClusterStartupRule.java:191)
>   
> at 
> org.apache.geode.management.internal.cli.commands.AlterRuntimeCommandDUnitTest.alterStatArchiveFileWithMember_updatesSelectedServerConfigs(AlterRuntimeCommandDUnitTest.java:466)
>   
>   
> Caused by:
>   
> org.apache.geode.GemFireConfigException: Unable to join the 
> distributed system.  Operation either timed out, was stopped or Locator does 
> not exist.
> {code}



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


[jira] [Updated] (GEODE-5703) CI Failure: GemFireConfigException in GMSMembershipManager.join() when trying to create Cache

2021-08-20 Thread Donal Evans (Jira)


 [ 
https://issues.apache.org/jira/browse/GEODE-5703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donal Evans updated GEODE-5703:
---
Summary: CI Failure: GemFireConfigException in GMSMembershipManager.join() 
when trying to create Cache  (was: CI Failure: GemFireConfigException)

> CI Failure: GemFireConfigException in GMSMembershipManager.join() when trying 
> to create Cache
> -
>
> Key: GEODE-5703
> URL: https://issues.apache.org/jira/browse/GEODE-5703
> Project: Geode
>  Issue Type: Bug
>Reporter: Hale Bales
>Priority: Major
>  Labels: swat
> Attachments: TestResultsPage.htm
>
>
> CI Failure can be found here:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/363
> Failed with Stack Trace:
> {code:java}
> org.apache.geode.management.internal.cli.commands.AlterRuntimeCommandDUnitTest
>  > alterStatArchiveFileWithMember_updatesSelectedServerConfigs(true) [0] 
> FAILED
>   
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.test.dunit.rules.ClusterStartupRule$$Lambda$41/1318057984.call
>  in VM 0 running on Host fca019e1fb13 with 4 VMs
>   
> at org.apache.geode.test.dunit.VM.invoke(VM.java:450)
>   
> at org.apache.geode.test.dunit.VM.invoke(VM.java:419)
>   
> at org.apache.geode.test.dunit.VM.invoke(VM.java:385)
>   
> at 
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startLocatorVM(ClusterStartupRule.java:198)
>   
> at 
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startLocatorVM(ClusterStartupRule.java:191)
>   
> at 
> org.apache.geode.management.internal.cli.commands.AlterRuntimeCommandDUnitTest.alterStatArchiveFileWithMember_updatesSelectedServerConfigs(AlterRuntimeCommandDUnitTest.java:466)
>   
>   
> Caused by:
>   
> org.apache.geode.GemFireConfigException: Unable to join the 
> distributed system.  Operation either timed out, was stopped or Locator does 
> not exist.
> {code}



--
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

2021-08-20 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on GEODE-9460:


Commit 6c1bf752dd3a4913ad319303a46e3ff2045d970e in geode's branch 
refs/heads/expireAuthentication from Joris Melchior
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=6c1bf75 ]

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] [Created] (GEODE-9530) CI Failure: ClassNotFoundException in TomcatSessionBackwardsCompatibilityTomcat7079WithOldModuleCanDoPutsTest

2021-08-20 Thread Donal Evans (Jira)
Donal Evans created GEODE-9530:
--

 Summary: CI Failure: ClassNotFoundException in 
TomcatSessionBackwardsCompatibilityTomcat7079WithOldModuleCanDoPutsTest
 Key: GEODE-9530
 URL: https://issues.apache.org/jira/browse/GEODE-9530
 Project: Geode
  Issue Type: Bug
Affects Versions: 1.14.0
Reporter: Donal Evans


{noformat}
org.apache.geode.session.tests.TomcatSessionBackwardsCompatibilityTomcat7079WithOldModuleCanDoPutsTest
 > initializationError FAILED
java.lang.ClassNotFoundException: 
org.apache.geode.session.tests.TomcatSessionBackwardsCompatibilityTomcat7079WithOldModuleCanDoPutsTest
at java.net.URLClassLoader.findClass(URLClassLoader.java:382)
at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)
at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:348)
at 
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:67)
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:35)
at 
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at 
org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
at 
org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
at 
org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:118)
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:35)
at 
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at 
org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:175)
at 
org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:157)
at 
org.gradle.internal.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:404)
at 
org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
at 
org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46)
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:55)
at java.lang.Thread.run(Thread.java:748)
{noformat}

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=  Test Results URI 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0770/test-results/upgradeTest/1619235491/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Test report artifacts from this job are available at:

http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0770/test-artifacts/1619235491/upgradetestfiles-OpenJDK8-1.14.0-build.0770.tgz

The above artifacts also contain an unrelated failure in 
RollingUpgradeRollSingleLocatorWithMultipleServersReplicatedRegion which was 
marked as GEODE-5703.



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


[jira] [Updated] (GEODE-9530) CI Failure: ClassNotFoundException in TomcatSessionBackwardsCompatibilityTomcat7079WithOldModuleCanDoPutsTest

2021-08-20 Thread Donal Evans (Jira)


 [ 
https://issues.apache.org/jira/browse/GEODE-9530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donal Evans updated GEODE-9530:
---
Labels: blocks-1.14.0​  (was: )

> CI Failure: ClassNotFoundException in 
> TomcatSessionBackwardsCompatibilityTomcat7079WithOldModuleCanDoPutsTest
> -
>
> Key: GEODE-9530
> URL: https://issues.apache.org/jira/browse/GEODE-9530
> Project: Geode
>  Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Donal Evans
>Priority: Major
>  Labels: blocks-1.14.0​
>
> {noformat}
> org.apache.geode.session.tests.TomcatSessionBackwardsCompatibilityTomcat7079WithOldModuleCanDoPutsTest
>  > initializationError FAILED
> java.lang.ClassNotFoundException: 
> org.apache.geode.session.tests.TomcatSessionBackwardsCompatibilityTomcat7079WithOldModuleCanDoPutsTest
>   at java.net.URLClassLoader.findClass(URLClassLoader.java:382)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
>   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
>   at java.lang.Class.forName0(Native Method)
>   at java.lang.Class.forName(Class.java:348)
>   at 
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:67)
>   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:35)
>   at 
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
>   at 
> org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
>   at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
>   at 
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:118)
>   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:35)
>   at 
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
>   at 
> org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:175)
>   at 
> org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:157)
>   at 
> org.gradle.internal.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:404)
>   at 
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
>   at 
> org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46)
>   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:55)
>   at java.lang.Thread.run(Thread.java:748)
> {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=  Test Results URI 
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0770/test-results/upgradeTest/1619235491/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0770/test-artifacts/1619235491/upgradetestfiles-OpenJD

[jira] [Created] (GEODE-9531) CI Failure: TxCommitMessageBCClientToServerTxPartitionTest fails with ForcedDisconnectException

2021-08-20 Thread Donal Evans (Jira)
Donal Evans created GEODE-9531:
--

 Summary: 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


{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.sendViaMembershipManager(ClusterDistributionManager.java:2053)
  at 
org.apache.geode.distributed.internal.ClusterDistributionManager.sendOutgoing(ClusterDistributionManager.java:1981)
  at 
org.apache.geode.distributed.internal.ClusterDistributionManager.sendMessage(ClusterDistributionManager.java:2018)
  at 
org.apache.geode.distributed.internal.ClusterDistributionManager.putOutgoing(ClusterDistributionManager.java:1083)
  at 
org.apache.geode.internal.cache.CreateReg

[jira] [Commented] (GEODE-9531) CI Failure: TxCommitMessageBCClientToServerTxPartitionTest fails with ForcedDisconnectException

2021-08-20 Thread Geode Integration (Jira)


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

Geode Integration commented on GEODE-9531:
--

Seen on support/1.14 in [UpgradeTestOpenJDK8 
#77|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/UpgradeTestOpenJDK8/builds/77]
 ... see [test 
results|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0787/test-results/upgradeTest/1621966586/]
 or download 
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0787/test-artifacts/1621966586/upgradetestfiles-OpenJDK8-1.14.0-build.0787.tgz].

> 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
>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 
> becaus

[jira] [Updated] (GEODE-9531) CI Failure: TxCommitMessageBCClientToServerTxPartitionTest fails with ForcedDisconnectException

2021-08-20 Thread Donal Evans (Jira)


 [ 
https://issues.apache.org/jira/browse/GEODE-9531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donal Evans updated GEODE-9531:
---
Labels: blocks-1.14.0​  (was: )

> 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
>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.sendViaMembershipManager(ClusterDistr

[jira] [Commented] (GEODE-6331) WANRollingUpgradeSecondaryEventsNotReprocessedAfterOldSiteMemberFailover. testSecondaryEventsNotReprocessedAfterOldSiteMemberFailover fails to connect to VM

2021-08-20 Thread Geode Integration (Jira)


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

Geode Integration commented on GEODE-6331:
--

Seen on support/1.14 in [upgrade-test-openjdk8 
#13|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/upgrade-test-openjdk8/builds/13]
 ... see [test 
results|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0809/test-results/upgradeTest/1623778726/]
 or download 
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0809/test-artifacts/1623778726/upgradetestfiles-openjdk8-1.14.0-build.0809.tgz].

> WANRollingUpgradeSecondaryEventsNotReprocessedAfterOldSiteMemberFailover. 
> testSecondaryEventsNotReprocessedAfterOldSiteMemberFailover fails to connect 
> to VM
> 
>
> Key: GEODE-6331
> URL: https://issues.apache.org/jira/browse/GEODE-6331
> Project: Geode
>  Issue Type: Bug
>Reporter: Dale Emery
>Priority: Major
>  Labels: flaky
>
> Three tests failed in a pre-checkin: 
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-pr/jobs/UpgradeTestOpenJDK8/builds/891]
> [http://files.apachegeode-ci.info/builds/apache-develop-pr/geode-pr-3128/test-results/upgradeTest/1548465524/]
> The first test failed in `GfshCommandRule.after()`:
> {noformat}
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.test.dunit.IgnoredException$1.run in VM 2 running on Host 
> 316152fb4a09 with 7 VMs with version 150
>   at org.apache.geode.test.dunit.VM.checkAvailability(VM.java:512)
>   at org.apache.geode.test.dunit.VM.invoke(VM.java:364)
>   at org.apache.geode.test.dunit.Invoke.invokeInEveryVM(Invoke.java:59)
>   at org.apache.geode.test.dunit.Invoke.invokeInEveryVM(Invoke.java:48)
>   at 
> org.apache.geode.test.dunit.IgnoredException.remove(IgnoredException.java:114)
>   at 
> org.apache.geode.test.junit.rules.GfshCommandRule.after(GfshCommandRule.java:128)
>   at 
> org.apache.geode.test.junit.rules.DescribedExternalResource$1.evaluate(DescribedExternalResource.java:42)
>   at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
>   at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at org.junit.runners.Suite.runChild(Suite.java:128)
>   at org.junit.runners.Suite.runChild(Suite.java:27)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   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:66)
>   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

[jira] [Assigned] (GEODE-9527) SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12

2021-08-20 Thread Ernest Burghardt (Jira)


 [ 
https://issues.apache.org/jira/browse/GEODE-9527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ernest Burghardt reassigned GEODE-9527:
---

Assignee: Ernest Burghardt

> 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: blocks-1.12.5, blocks-1.13.5, blocks-1.14.0​
>
> This fails the most on Windows, but also on Linux.  It seems to happen much 
> more on 1.12 and 1.13, but also seen on 1.14.  However not seen on 
> develop...so maybe there is some fix already that just needs to be 
> backported?  If so please close this as a dupe.
> {noformat}
> org.apache.geode.experimental.driver.SSLTest > 
> driverCannotConnectIfProtocolsMismatch FAILED
> java.lang.AssertionError: 
> Expected: an instance of javax.net.ssl.SSLException
>  but:  is a 
> java.net.SocketException
> Stacktrace was: java.net.SocketException: Connection reset
>   at java.base/java.net.SocketInputStream.read(SocketInputStream.java:186)
>   at java.base/java.net.SocketInputStream.read(SocketInputStream.java:140)
>   at 
> java.base/sun.security.ssl.SSLSocketInputRecord.read(SSLSocketInputRecord.java:478)
>   at 
> java.base/sun.security.ssl.SSLSocketInputRecord.readHeader(SSLSocketInputRecord.java:472)
>   at 
> java.base/sun.security.ssl.SSLSocketInputRecord.decode(SSLSocketInputRecord.java:160)
>   at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:111)
>   at 
> java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1426)
>   at 
> java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1336)
>   at 
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:450)
>   at 
> java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:421)
>   at 
> org.apache.geode.experimental.driver.SocketFactory.connect(SocketFactory.java:146)
>   at 
> org.apache.geode.experimental.driver.ProtobufChannel.createSocket(ProtobufChannel.java:232)
>   at 
> org.apache.geode.experimental.driver.ProtobufChannel.findAServer(ProtobufChannel.java:116)
>   at 
> org.apache.geode.experimental.driver.ProtobufChannel.connectToAServer(ProtobufChannel.java:66)
>   at 
> org.apache.geode.experimental.driver.ProtobufChannel.(ProtobufChannel.java:49)
>   at 
> org.apache.geode.experimental.driver.ProtobufDriver.(ProtobufDriver.java:60)
>   at 
> org.apache.geode.experimental.driver.DriverFactory.create(DriverFactory.java:154)
>   at 
> org.apache.geode.experimental.driver.SSLTest.driverCannotConnectIfProtocolsMismatch(SSLTest.java:190)
> {noformat}



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


[jira] [Commented] (GEODE-9523) ContainerInstall Resource path invalid on Windows

2021-08-20 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on GEODE-9523:


Commit 2752849e28711f27fdc41556984358583b5fc012 in geode's branch 
refs/heads/develop 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
>
> The {{ContainerInstall}} test helper creates an installer using this code:
> {noformat}
> String resource = getResource(getClass(), "/" + downloadURL).getPath();
> URL url = Paths.get(resource).toUri().toURL();
> Installer installer = new ZipURLInstaller(url, TMP_DIR + "/downloads", 
> installDir);
> {noformat}
> On Windows, the {{resource}} string is not a valid {{Path}}, and the second 
> line throws an exception:
> _java.nio.file.InvalidPathException: Illegal char <:> at index 2: 
> /C:/Users/geode/geode/geode-assembly/build/resources/distributedTest/tomcat-9.0.48.zip_
> The chain of conversions is unnecessary. On Windows, the URL returned from 
> {{getResource(...)}} is a perfectly fine URL to pass to the 
> {{ZipURLInstaller}}.



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


[jira] [Updated] (GEODE-9526) DiskStore test incorrectly treats absolute path as relative on Windows

2021-08-20 Thread Dale Emery (Jira)


 [ 
https://issues.apache.org/jira/browse/GEODE-9526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dale Emery updated GEODE-9526:
--
Labels: GeodeOperationAPI pull-request-available  (was: 
pull-request-available)

> 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
>
> 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] [Assigned] (GEODE-9526) DiskStore test incorrectly treats absolute path as relative on Windows

2021-08-20 Thread Dale Emery (Jira)


 [ 
https://issues.apache.org/jira/browse/GEODE-9526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dale Emery reassigned GEODE-9526:
-

Assignee: Dale Emery

> 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: pull-request-available
>
> On Windows, an absolute file path can begin with a letter (e.g. "C:\…"). 
> {{DiskStoreCommandsDUnitTest.verifyDiskStoreInServer(...)}} incorrectly 
> assumes that, because such a path does not start with a file separator, it 
> must be relative. It then attempts to convert it to an absolute path by 
> prepending the current directory onto it:
> {noformat}
> String absoluteDiskDirectoryName = 
> diskDirectoryName.startsWith(File.separator)
> ? diskDirectoryName
> : CURRENT_DIRECTORY + File.separator + diskDirectoryName;
> {noformat}
> On Windows, the resulting file path is unusable.



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


[jira] [Resolved] (GEODE-9523) ContainerInstall Resource path invalid on Windows

2021-08-20 Thread Dale Emery (Jira)


 [ 
https://issues.apache.org/jira/browse/GEODE-9523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dale Emery resolved GEODE-9523.
---
Fix Version/s: 1.15.0
   Resolution: Fixed

> 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] [Closed] (GEODE-9523) ContainerInstall Resource path invalid on Windows

2021-08-20 Thread Dale Emery (Jira)


 [ 
https://issues.apache.org/jira/browse/GEODE-9523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dale Emery closed GEODE-9523.
-

> 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] [Resolved] (GEODE-9526) DiskStore test incorrectly treats absolute path as relative on Windows

2021-08-20 Thread Dale Emery (Jira)


 [ 
https://issues.apache.org/jira/browse/GEODE-9526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dale Emery resolved GEODE-9526.
---
Fix Version/s: 1.15.0
   Resolution: Fixed

> 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] [Closed] (GEODE-9526) DiskStore test incorrectly treats absolute path as relative on Windows

2021-08-20 Thread Dale Emery (Jira)


 [ 
https://issues.apache.org/jira/browse/GEODE-9526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dale Emery closed GEODE-9526.
-

> 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-9526) DiskStore test incorrectly treats absolute path as relative on Windows

2021-08-20 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on GEODE-9526:


Commit 0d1954bbabccf7cc466392c48ecfd82df664b1b9 in geode's branch 
refs/heads/develop 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] [Created] (GEODE-9532) CI Failure: DiskDistributedNoAckAsyncRegionDUnitTest > testNoDataSerializer fails with NotSerializableException

2021-08-20 Thread Donal Evans (Jira)
Donal Evans created GEODE-9532:
--

 Summary: 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


{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  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  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(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:17

[jira] [Updated] (GEODE-9532) CI Failure: DiskDistributedNoAckAsyncRegionDUnitTest > testNoDataSerializer fails with NotSerializableException

2021-08-20 Thread Donal Evans (Jira)


 [ 
https://issues.apache.org/jira/browse/GEODE-9532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donal Evans updated GEODE-9532:
---
Labels: blocks-1.14.0​  (was: )

> 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
>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(DiskEntry.java:753)
>   at 
> or

[jira] [Commented] (GEODE-9532) CI Failure: DiskDistributedNoAckAsyncRegionDUnitTest > testNoDataSerializer fails with NotSerializableException

2021-08-20 Thread Geode Integration (Jira)


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

Geode Integration commented on GEODE-9532:
--

Seen on support/1.14 in [distributed-test-openjdk8 
#14|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/distributed-test-openjdk8/builds/14]
 ... see [test 
results|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0809/test-results/distributedTest/1623780601/]
 or download 
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0809/test-artifacts/1623780601/distributedtestfiles-openjdk8-1.14.0-build.0809.tgz].

> 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
>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

[jira] [Updated] (GEODE-9527) SSLTest > driverCannotConnectIfProtocolsMismatch fails often on JDK 11.0.12

2021-08-20 Thread ASF GitHub Bot (Jira)


 [ 
https://issues.apache.org/jira/browse/GEODE-9527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated GEODE-9527:
--
Labels: blocks-1.12.5 blocks-1.13.5 blocks-1.14.0​ pull-request-available  
(was: blocks-1.12.5 blocks-1.13.5 blocks-1.14.0​)

> 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: blocks-1.12.5, blocks-1.13.5, blocks-1.14.0​, 
> 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] [Assigned] (GEODE-9347) Make Publish and Subscribe use Map data structures

2021-08-20 Thread Donal Evans (Jira)


 [ 
https://issues.apache.org/jira/browse/GEODE-9347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donal Evans reassigned GEODE-9347:
--

Assignee: (was: Donal Evans)

> Make Publish and Subscribe use Map data structures
> --
>
> Key: GEODE-9347
> URL: https://issues.apache.org/jira/browse/GEODE-9347
> Project: Geode
>  Issue Type: Improvement
>  Components: redis
>Reporter: John Hutchison
>Priority: Major
>
> our current implementation of Publish and Subscribe use a list of 
> Subscription objects to maintain state.
> @doevans noticed that native redis is using 2 maps to maintain state
> in an effort to mimic native redis data structures and hopefully improve 
> performance, our publish and subscribe commands should also use maps 1) 
> (channel -> all subscribers). 2) subsrciber(client) -> all subscribed channels



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


[jira] [Created] (GEODE-9533) CI Failure: RedisSessionDUnitTest fails due to BindException

2021-08-20 Thread Donal Evans (Jira)
Donal Evans created GEODE-9533:
--

 Summary: 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


{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] [Commented] (GEODE-9533) CI Failure: RedisSessionDUnitTest fails due to BindException

2021-08-20 Thread Geode Integration (Jira)


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

Geode Integration commented on GEODE-9533:
--

Seen on support/1.14 in [distributed-test-openjdk8 
#32|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-14-main/jobs/distributed-test-openjdk8/builds/32]
 ... see [test 
results|http://files.apachegeode-ci.info/builds/apache-support-1-14-main/1.14.0-build.0837/test-results/distributedTest/1628717583/]
 or download 
[artifacts|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].

> 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
>
> {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-9534) Add tests to verify peer communication when auth expired

2021-08-20 Thread Jinmei Liao (Jira)
Jinmei Liao created GEODE-9534:
--

 Summary: Add tests to verify peer communication when auth expired
 Key: GEODE-9534
 URL: https://issues.apache.org/jira/browse/GEODE-9534
 Project: Geode
  Issue Type: Sub-task
Reporter: Jinmei Liao


When a server joins the cluster, it needs to provide credentials, when network 
issue happens, the sever disconnects and reconnects back, what happens when the 
credential expired?



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


[jira] [Updated] (GEODE-9534) Add tests to verify peer communication when auth expired

2021-08-20 Thread Jinmei Liao (Jira)


 [ 
https://issues.apache.org/jira/browse/GEODE-9534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jinmei Liao updated GEODE-9534:
---
Labels: GeodeOperationAPI security  (was: )

> Add tests to verify peer communication when auth expired
> 
>
> Key: GEODE-9534
> URL: https://issues.apache.org/jira/browse/GEODE-9534
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Jinmei Liao
>Priority: Major
>  Labels: GeodeOperationAPI, security
>
> When a server joins the cluster, it needs to provide credentials, when 
> network issue happens, the sever disconnects and reconnects back, what 
> happens when the credential expired?



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


[jira] [Updated] (GEODE-9446) Remove unnecessary uses of byte[] in RedisSortedSet

2021-08-20 Thread ASF GitHub Bot (Jira)


 [ 
https://issues.apache.org/jira/browse/GEODE-9446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated GEODE-9446:
--
Labels: pull-request-available  (was: )

> Remove unnecessary uses of byte[] in RedisSortedSet
> ---
>
> Key: GEODE-9446
> URL: https://issues.apache.org/jira/browse/GEODE-9446
> Project: Geode
>  Issue Type: Improvement
>  Components: redis
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Assignee: Hale Bales
>Priority: Major
>  Labels: pull-request-available
>
> The current implementation of {{RedisSortedSet}} uses an 
> {{AbstractOrderedStatisticsEntry}} class containing both {{double}} score and 
> {{byte[]}} scoreBytes fields. The {{double}} field is required to allow the 
> sorting behaviour required of the data structure, but the {{byte[]}} field is 
> not necessary except when returning results to the client.
> The class should be refactored to eliminate the {{byte[]}} scoreBytes field 
> from {{AbstractOrderedStatisticsEntry}} and reduce the memory overhead of 
> operations.
> As part of this refactoring, the below call to {{members.put()}} should be 
> removed from {{memberAdd()}} as it will no longer be necessary.
> {code:java}
> protected synchronized byte[] memberAdd(byte[] memberToAdd, byte[] 
> scoreToAdd) {
> ...
> } else {
>   scoreSet.remove(existingEntry);
>   byte[] oldScore = existingEntry.scoreBytes;
>   existingEntry.updateScore(stripTrailingZeroFromDouble(scoreToAdd));
>   members.put(memberToAdd, existingEntry); <<< remove this
>   scoreSet.add(existingEntry);
>   return oldScore;
> }
> {code}
> Also, uses of the {{stripTrailingZeroFromDouble()}} method should be moved to 
> just prior to the response being returned to the client, to ensure that the 
> format of the returned String representations of double values match native 
> Redis.



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


[jira] [Assigned] (GEODE-9071) CI Failure: PartitionedRegionCqQueryDUnitTest > testRemoveAllWithCQLocalDestroy

2021-08-20 Thread Eric Shu (Jira)


 [ 
https://issues.apache.org/jira/browse/GEODE-9071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eric Shu reassigned GEODE-9071:
---

Assignee: Eric Shu

> 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: caching-applications
>
> {noformat}
> org.apache.geode.cache.query.cq.dunit.PartitionedRegionCqQueryDUnitTest > 
> testRemoveAllWithCQLocalDestroy FAILED
> 10:10:22org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.cache.query.cq.dunit.PartitionedRegionCqQueryDUnitTest$$Lambda$87/434016892.run
>  in VM 2 running on Host bb8c1d338b8b with 4 VMs
> 10:10:22at 
> org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
> 10:10:22at org.apache.geode.test.dunit.VM.invoke(VM.java:448)
> 10:10:22at 
> org.apache.geode.cache.query.cq.dunit.PartitionedRegionCqQueryDUnitTest.testRemoveAllWithCQLocalDestroy(PartitionedRegionCqQueryDUnitTest.java:243)
> 10:10:22
> 10:10:22Caused by:
> 10:10:22org.junit.ComparisonFailure: expected:<[999]> but was:<[645]>
> 10:10:22at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> 10:10:22at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> 10:10:22at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> 10:10:22at 
> org.apache.geode.cache.query.cq.dunit.PartitionedRegionCqQueryDUnitTest.lambda$testRemoveAllWithCQLocalDestroy$c93719d5$3(PartitionedRegionCqQueryDUnitTest.java:251)
>  {noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI 
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0082/test-results/distributedTest/1616696789/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0082/test-artifacts/1616696789/distributedtestfiles-OpenJDK8-1.15.0-build.0082.tgz



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


[jira] [Updated] (GEODE-9347) Make Publish and Subscribe use Map data structures

2021-08-20 Thread Donal Evans (Jira)


 [ 
https://issues.apache.org/jira/browse/GEODE-9347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Donal Evans updated GEODE-9347:
---
Description: 
our current implementation of Publish and Subscribe use a list of Subscription 
objects to maintain state.

@doevans noticed that native redis is using 2 maps to maintain state

in an effort to mimic native redis data structures and hopefully improve 
performance, our publish and subscribe commands should also use maps 1) 
(channel -> all subscribers). 2) subsrciber(client) -> all subscribed channels

Updated 08/20/2021:

Redis handles subscriptions as follows:
* Each client object maintains a set of channels to which it is subscribed
* Each client object maintains a list of patterns to which it is subscribed
* The server maintains a map of channels -> subscribed clients
* The server maintains a list of all Pattern objects
* Each Pattern object knows which client is subscribed to it and the byte[] 
pattern associated with it

On subscribe:
* Add the channel to the client's set of subscribed clients
* Add the channel to the server's map of channels -> subscribed clients
* Respond with the total number of subscribed channels and patterns for the 
client (sum the sizes of the client's channel set and pattern list)

On psubscribe:
* Add the byte[] pattern to the client's list of patterns
* Create a Pattern object and add it to the server's list of Patterns
* Respond with the total number of subscribed channels and patterns for the 
client (sum the sizes of the client's channel set and pattern list)

On publish:
* Notify all clients subscribed to the channel using the server's channels -> 
subscribed clients map
* Notify all clients subscribed to matching channels by comparing the channel 
to the server's list of all patterns using Glob-style matching
* Respond with the number of notifications sent

For our implementation, a similar approach can be used, but this will entail 
significant refactoring of PubSub classes

  was:
our current implementation of Publish and Subscribe use a list of Subscription 
objects to maintain state.

@doevans noticed that native redis is using 2 maps to maintain state

in an effort to mimic native redis data structures and hopefully improve 
performance, our publish and subscribe commands should also use maps 1) 
(channel -> all subscribers). 2) subsrciber(client) -> all subscribed channels




> Make Publish and Subscribe use Map data structures
> --
>
> Key: GEODE-9347
> URL: https://issues.apache.org/jira/browse/GEODE-9347
> Project: Geode
>  Issue Type: Improvement
>  Components: redis
>Reporter: John Hutchison
>Priority: Major
>
> our current implementation of Publish and Subscribe use a list of 
> Subscription objects to maintain state.
> @doevans noticed that native redis is using 2 maps to maintain state
> in an effort to mimic native redis data structures and hopefully improve 
> performance, our publish and subscribe commands should also use maps 1) 
> (channel -> all subscribers). 2) subsrciber(client) -> all subscribed channels
> Updated 08/20/2021:
> Redis handles subscriptions as follows:
> * Each client object maintains a set of channels to which it is subscribed
> * Each client object maintains a list of patterns to which it is subscribed
> * The server maintains a map of channels -> subscribed clients
> * The server maintains a list of all Pattern objects
> * Each Pattern object knows which client is subscribed to it and the byte[] 
> pattern associated with it
> On subscribe:
> * Add the channel to the client's set of subscribed clients
> * Add the channel to the server's map of channels -> subscribed clients
> * Respond with the total number of subscribed channels and patterns for the 
> client (sum the sizes of the client's channel set and pattern list)
> On psubscribe:
> * Add the byte[] pattern to the client's list of patterns
> * Create a Pattern object and add it to the server's list of Patterns
> * Respond with the total number of subscribed channels and patterns for the 
> client (sum the sizes of the client's channel set and pattern list)
> On publish:
> * Notify all clients subscribed to the channel using the server's channels -> 
> subscribed clients map
> * Notify all clients subscribed to matching channels by comparing the channel 
> to the server's list of all patterns using Glob-style matching
> * Respond with the number of notifications sent
> For our implementation, a similar approach can be used, but this will entail 
> significant refactoring of PubSub classes



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


[jira] [Commented] (GEODE-9529) fix release scripts

2021-08-20 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on GEODE-9529:


Commit 9ff39d12361e668657413b8cbfc9558b71795a96 in geode's branch 
refs/heads/develop 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
>
> * 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] [Updated] (GEODE-9071) CI Failure: PartitionedRegionCqQueryDUnitTest > testRemoveAllWithCQLocalDestroy

2021-08-20 Thread Eric Shu (Jira)


 [ 
https://issues.apache.org/jira/browse/GEODE-9071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eric Shu updated GEODE-9071:

Labels: GeodeOperationAPI  (was: caching-applications)

> 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
>
> {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] [Assigned] (GEODE-9241) CI failure in PartitionedRegionCqQueryDUnitTest > testPutAllWithCQLocalDestroy

2021-08-20 Thread Eric Shu (Jira)


 [ 
https://issues.apache.org/jira/browse/GEODE-9241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eric Shu reassigned GEODE-9241:
---

Assignee: Eric Shu

> 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: caching-applications, 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] [Updated] (GEODE-9241) CI failure in PartitionedRegionCqQueryDUnitTest > testPutAllWithCQLocalDestroy

2021-08-20 Thread Eric Shu (Jira)


 [ 
https://issues.apache.org/jira/browse/GEODE-9241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eric Shu updated GEODE-9241:

Labels: GeodeOperationAPI release-blocker  (was: caching-applications 
release-blocker)

> 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-9529) fix release scripts

2021-08-20 Thread Owen Nichols (Jira)


 [ 
https://issues.apache.org/jira/browse/GEODE-9529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Owen Nichols resolved GEODE-9529.
-
Fix Version/s: 1.15.0
   Resolution: Fixed

> 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] [Updated] (GEODE-9071) CI Failure: PartitionedRegionCqQueryDUnitTest > testRemoveAllWithCQLocalDestroy

2021-08-20 Thread ASF GitHub Bot (Jira)


 [ 
https://issues.apache.org/jira/browse/GEODE-9071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated GEODE-9071:
--
Labels: GeodeOperationAPI pull-request-available  (was: GeodeOperationAPI)

> 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)