[jira] [Commented] (GEODE-9369) Command to copy region entries from a WAN site to another.
[ https://issues.apache.org/jira/browse/GEODE-9369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404875#comment-17404875 ] Geode Integration commented on GEODE-9369: -- Seen in [distributed-test-openjdk11 #149|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/distributed-test-openjdk11/builds/149] ... see [test results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0437/test-results/distributedTest/1629932984/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0437/test-artifacts/1629932984/distributedtestfiles-openjdk11-1.15.0-build.0437.tgz]. > Command to copy region entries from a WAN site to another. > -- > > Key: GEODE-9369 > URL: https://issues.apache.org/jira/browse/GEODE-9369 > Project: Geode > Issue Type: New Feature > Components: wan >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > As described in RFC: > [https://cwiki.apache.org/confluence/display/GEODE/Geode+Command+to+replicate+region+data+from+one+site+to+another+connected+via+WAN] > it is proposed to implement a command that copies the entries of a region in > a WAN site to the same region in another WAN site by using WAN replication. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (GEODE-9537) CqDataUsingPoolDUnitTest (and CqDataUsingPoolOptimizedExecuteDUnitTest) should not use ephemeral ports
[
https://issues.apache.org/jira/browse/GEODE-9537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen Nichols updated GEODE-9537:
Comment: was deleted
(was: Seen in [distributed-test-openjdk11
#149|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/distributed-test-openjdk11/builds/149]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0437/test-results/distributedTest/1629932984/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0437/test-artifacts/1629932984/distributedtestfiles-openjdk11-1.15.0-build.0437.tgz].)
> CqDataUsingPoolDUnitTest (and CqDataUsingPoolOptimizedExecuteDUnitTest)
> should not use ephemeral ports
> --
>
> Key: GEODE-9537
> URL: https://issues.apache.org/jira/browse/GEODE-9537
> Project: Geode
> Issue Type: Test
> Components: tests
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
> Labels: pull-request-available
>
> These tests currently use ephemeral ports for components that are stopped and
> restarted during the test. It can happen that other, concurrently running
> tests, will start using these same ports causing test failures (but not in
> the tests mentioned here).
> Test failures appear as dunit suspect strings:
> {noformat}
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in 'dunit_suspect-locator.log' at line 347
> [fatal 2021/08/21 19:46:08.527 UTC tid=47]
> Exception in processing request from 10.0.0.107
> java.lang.Exception: Improperly configured client detected - use
> addPoolLocator to configure its locators instead of addPoolServer.
> at
> org.apache.geode.distributed.internal.ProtocolCheckerImpl.checkProtocol(ProtocolCheckerImpl.java:31)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:342)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9464) Add a non-Steeltoe Asp.Net Core SessionState sample app to SessionStateCore
[
https://issues.apache.org/jira/browse/GEODE-9464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404800#comment-17404800
]
ASF GitHub Bot commented on GEODE-9464:
---
pivotal-jbarrett commented on a change in pull request #856:
URL: https://github.com/apache/geode-native/pull/856#discussion_r696195470
##
File path: netcore/AspNetCore GeodeSession
Sample/Middleware/HttpContextItemsMiddleware.cs
##
@@ -0,0 +1,52 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+using System;
+using System.Threading.Tasks;
+using Microsoft.AspNetCore.Builder;
+using Microsoft.AspNetCore.Http;
+
+namespace SessionSample.Middleware
+{
+#region snippet1
Review comment:
Formatting
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscr...@geode.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Add a non-Steeltoe Asp.Net Core SessionState sample app to SessionStateCore
> ---
>
> Key: GEODE-9464
> URL: https://issues.apache.org/jira/browse/GEODE-9464
> Project: Geode
> Issue Type: Test
> Components: native client
>Reporter: Michael Martell
>Priority: Major
> Labels: pull-request-available
>
> The current Asp.Net sample app uses Steeltoe for discovery and registration
> of our sessionstate provider. We need a non-Steeltoe sample as well, since
> not everyone uses Steeltoe.
> This will be a good test of our NuGet access to the SessionState Core
> artifacts and its dependencies.
> Note: Ensure that the web application runs on all platforms.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9537) CqDataUsingPoolDUnitTest (and CqDataUsingPoolOptimizedExecuteDUnitTest) should not use ephemeral ports
[
https://issues.apache.org/jira/browse/GEODE-9537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404798#comment-17404798
]
Geode Integration commented on GEODE-9537:
--
Seen in [distributed-test-openjdk11
#149|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/distributed-test-openjdk11/builds/149]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0437/test-results/distributedTest/1629932984/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0437/test-artifacts/1629932984/distributedtestfiles-openjdk11-1.15.0-build.0437.tgz].
> CqDataUsingPoolDUnitTest (and CqDataUsingPoolOptimizedExecuteDUnitTest)
> should not use ephemeral ports
> --
>
> Key: GEODE-9537
> URL: https://issues.apache.org/jira/browse/GEODE-9537
> Project: Geode
> Issue Type: Test
> Components: tests
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
> Labels: pull-request-available
>
> These tests currently use ephemeral ports for components that are stopped and
> restarted during the test. It can happen that other, concurrently running
> tests, will start using these same ports causing test failures (but not in
> the tests mentioned here).
> Test failures appear as dunit suspect strings:
> {noformat}
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in 'dunit_suspect-locator.log' at line 347
> [fatal 2021/08/21 19:46:08.527 UTC tid=47]
> Exception in processing request from 10.0.0.107
> java.lang.Exception: Improperly configured client detected - use
> addPoolLocator to configure its locators instead of addPoolServer.
> at
> org.apache.geode.distributed.internal.ProtocolCheckerImpl.checkProtocol(ProtocolCheckerImpl.java:31)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:342)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9464) Add a non-Steeltoe Asp.Net Core SessionState sample app to SessionStateCore
[ https://issues.apache.org/jira/browse/GEODE-9464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404787#comment-17404787 ] ASF GitHub Bot commented on GEODE-9464: --- mmartell commented on pull request #856: URL: https://github.com/apache/geode-native/pull/856#issuecomment-905947023 Thorough Mr. Barrett is. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@geode.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Add a non-Steeltoe Asp.Net Core SessionState sample app to SessionStateCore > --- > > Key: GEODE-9464 > URL: https://issues.apache.org/jira/browse/GEODE-9464 > Project: Geode > Issue Type: Test > Components: native client >Reporter: Michael Martell >Priority: Major > Labels: pull-request-available > > The current Asp.Net sample app uses Steeltoe for discovery and registration > of our sessionstate provider. We need a non-Steeltoe sample as well, since > not everyone uses Steeltoe. > This will be a good test of our NuGet access to the SessionState Core > artifacts and its dependencies. > Note: Ensure that the web application runs on all platforms. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9464) Add a non-Steeltoe Asp.Net Core SessionState sample app to SessionStateCore
[
https://issues.apache.org/jira/browse/GEODE-9464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404780#comment-17404780
]
ASF GitHub Bot commented on GEODE-9464:
---
pivotal-jbarrett commented on a change in pull request #856:
URL: https://github.com/apache/geode-native/pull/856#discussion_r696182426
##
File path: netcore/AspNetCore GeodeSession
Sample/Extensions/SessionExtensions.cs
##
@@ -0,0 +1,52 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+using System.Text.Json;
+using Microsoft.AspNetCore.Http;
+
+namespace Web.Extensions {
+#region snippet1
+ public static class SessionExtensions {
+public static void Set(this ISession session, string key, T value) {
+ session.SetString(key, JsonSerializer.Serialize(value));
+}
+
+public static T Get(this ISession session, string key) {
+ var value = session.GetString(key);
+ return value == null ? default : JsonSerializer.Deserialize(value);
+}
+ }
+#endregion
+}
+
+namespace Web.Extensions2 {
+ // Alternate approach
+
+ public static class SessionExtensions {
+public static void Set(this ISession session, string key, T value) {
+ session.SetString(key, JsonSerializer.Serialize(value));
+}
+
+public static bool TryGet(this ISession session, string key, out T
value) {
+ var state = session.GetString(key);
+ value = default;
+ if (state == null)
Review comment:
Always use `{}` braces.
##
File path: netcore/AspNetCore GeodeSession Sample/AspNetCore GeodeSession
Sample.csproj.user
##
@@ -0,0 +1,6 @@
+
+http://schemas.microsoft.com/developer/msbuild/2003;>
+
+IIS Express
+
+
Review comment:
New line
##
File path: netcore/AspNetCore GeodeSession Sample/Models/BasicAuthInitialize.cs
##
@@ -0,0 +1,47 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+using Apache.Geode.Client;
+using System;
+using System.Collections.Generic;
+
+namespace GemFireSessionState.Models
+{
+ public class BasicAuthInitialize : IAuthInitialize
+ {
+private string _username;
+private string _password;
+
+public BasicAuthInitialize(string username, string password)
+{
+ _username = username;
+ _password = password;
+}
+
+public void Close()
+{
+}
+
+public Dictionary GetCredentials()
+{
+ Console.WriteLine("SimpleAuthInitialize::GetCredentials called");
+ var credentials = new Dictionary();
+ credentials.Add("security-username", "root");
+ credentials.Add("security-password", "root-password");
+ return credentials;
+}
+ }
+}
Review comment:
New line
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscr...@geode.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Add a non-Steeltoe Asp.Net Core SessionState sample app to SessionStateCore
> ---
>
> Key: GEODE-9464
> URL: https://issues.apache.org/jira/browse/GEODE-9464
> Project: Geode
> Issue Type: Test
> Components: native client
>Reporter: Michael Martell
>
[jira] [Updated] (GEODE-9552) ForcedDisconnectException is not handled in ExecutionHandlerContext
[
https://issues.apache.org/jira/browse/GEODE-9552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-9552:
--
Labels: pull-request-available (was: )
> ForcedDisconnectException is not handled in ExecutionHandlerContext
> ---
>
> Key: GEODE-9552
> URL: https://issues.apache.org/jira/browse/GEODE-9552
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Priority: Major
> Labels: pull-request-available
>
> As part of the changes in GEODE-9303, handling of various exceptions related
> to function execution was removed from the
> {{ExecutionHandlerContext.getExceptionResponse()}} method. However,
> {{ForcedDisconnectException}} can still occur due to e.g. network partition,
> and so handling for this exception should be restored.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (GEODE-9320) CI Failure: SetNXNativeRedisAcceptanceTest > classMethod FAILED
[
https://issues.apache.org/jira/browse/GEODE-9320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404768#comment-17404768
]
Dan Smith edited comment on GEODE-9320 at 8/25/21, 11:30 PM:
-
Note, the most recent failure was not a port conflict but this error message.
Reopened GEODE-5252 for that. Leaving this open for the original port conflict
for now.
{noformat}
org.junit.ComparisonFailure: [Incorrect primary node count] expected:<[3]> but
was:<[2]>
at
jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at
org.apache.geode.redis.NativeRedisClusterTestRule.waitForPrimaries(NativeRedisClusterTestRule.java:156)
at
org.apache.geode.redis.NativeRedisClusterTestRule.access$100(NativeRedisClusterTestRule.java:44)
at
org.apache.geode.redis.NativeRedisClusterTestRule$1.evaluate(NativeRedisClusterTestRule.java:91)
at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
at
org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:62)
at
org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:566)
at
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:36)
at
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at
org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:33)
at
org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:94)
at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
at
org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:119)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:566)
at
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:36)
at
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at
org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:182)
at
org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:164)
at
org.gradle.internal.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:414)
at
org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
at
org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at
org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:56)
at java.lang.Thread.run(Thread.java:829)
{noformat}
was (Author: upthewaterspout):
Note, the most recent failure was not a port conflict but this error message
{noformat}
org.junit.ComparisonFailure: [Incorrect primary node count] expected:<[3]> but
was:<[2]>
at
jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
[jira] [Reopened] (GEODE-9252) CI failure: NativeRedisClusterTestRule incorrect primary node count (expected 3 but was 2)
[
https://issues.apache.org/jira/browse/GEODE-9252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith reopened GEODE-9252:
--
This happened again. Was reported against GEODE-9320 but is actually this issue.
Seen in [acceptance-test-openjdk11
#145|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/acceptance-test-openjdk11/builds/145]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0434/test-results/acceptanceTest/1629852506/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0434/test-artifacts/1629852506/acceptancetestfiles-openjdk11-1.15.0-build.0434.tgz].
> CI failure: NativeRedisClusterTestRule incorrect primary node count (expected
> 3 but was 2)
> --
>
> Key: GEODE-9252
> URL: https://issues.apache.org/jira/browse/GEODE-9252
> Project: Geode
> Issue Type: Bug
> Components: redis
>Reporter: Owen Nichols
>Assignee: Jens Deppe
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> {noformat}
> org.apache.geode.redis.internal.executor.hash.HashesNativeRedisAcceptanceTest
> > classMethod FAILED
> org.junit.ComparisonFailure: [Incorrect primary node count]
> expected:<[3]> but was:<[2]>
> at
> org.apache.geode.redis.NativeRedisClusterTestRule$1.evaluate(NativeRedisClusterTestRule.java:93)
> {noformat}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9252) CI failure: NativeRedisClusterTestRule incorrect primary node count (expected 3 but was 2)
[
https://issues.apache.org/jira/browse/GEODE-9252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404778#comment-17404778
]
Dan Smith commented on GEODE-9252:
--
On the face of it, 5 seconds seems like too short of a time to avoid having
flaky tests on a CI machine. Maybe we should just up the timeout where we are
waiting for primary nodes?
> CI failure: NativeRedisClusterTestRule incorrect primary node count (expected
> 3 but was 2)
> --
>
> Key: GEODE-9252
> URL: https://issues.apache.org/jira/browse/GEODE-9252
> Project: Geode
> Issue Type: Bug
> Components: redis
>Reporter: Owen Nichols
>Assignee: Jens Deppe
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> {noformat}
> org.apache.geode.redis.internal.executor.hash.HashesNativeRedisAcceptanceTest
> > classMethod FAILED
> org.junit.ComparisonFailure: [Incorrect primary node count]
> expected:<[3]> but was:<[2]>
> at
> org.apache.geode.redis.NativeRedisClusterTestRule$1.evaluate(NativeRedisClusterTestRule.java:93)
> {noformat}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9464) Add a non-Steeltoe Asp.Net Core SessionState sample app to SessionStateCore
[
https://issues.apache.org/jira/browse/GEODE-9464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404773#comment-17404773
]
ASF GitHub Bot commented on GEODE-9464:
---
mmartell commented on a change in pull request #856:
URL: https://github.com/apache/geode-native/pull/856#discussion_r696179120
##
File path: netcore/AspNetCore GeodeSession Sample/Properties/launchSettings.json
##
@@ -0,0 +1,28 @@
+{
+ "iisSettings": {
+"windowsAuthentication": false,
+"anonymousAuthentication": true,
+"iisExpress": {
+ "applicationUrl": "http://localhost:50795/;,
+ "sslPort": 44315
+}
+ },
+ "profiles": {
+"IIS Express": {
+ "commandName": "IISExpress",
+ "launchBrowser": true,
+ "environmentVariables": {
+"ASPNETCORE_ENVIRONMENT": "Development"
+ },
+ "nativeDebugging": true
+},
+"SessionSample": {
+ "commandName": "Project",
+ "launchBrowser": true,
+ "environmentVariables": {
+"ASPNETCORE_ENVIRONMENT": "Development"
+ },
+ "applicationUrl": "https://localhost:5001;http://localhost:5000;
+}
+ }
+}
Review comment:
Good catch.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscr...@geode.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Add a non-Steeltoe Asp.Net Core SessionState sample app to SessionStateCore
> ---
>
> Key: GEODE-9464
> URL: https://issues.apache.org/jira/browse/GEODE-9464
> Project: Geode
> Issue Type: Test
> Components: native client
>Reporter: Michael Martell
>Priority: Major
> Labels: pull-request-available
>
> The current Asp.Net sample app uses Steeltoe for discovery and registration
> of our sessionstate provider. We need a non-Steeltoe sample as well, since
> not everyone uses Steeltoe.
> This will be a good test of our NuGet access to the SessionState Core
> artifacts and its dependencies.
> Note: Ensure that the web application runs on all platforms.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9369) Command to copy region entries from a WAN site to another.
[ https://issues.apache.org/jira/browse/GEODE-9369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404772#comment-17404772 ] Geode Integration commented on GEODE-9369: -- Seen in [windows-unit-test-openjdk11 #145|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/windows-unit-test-openjdk11/builds/145] ... see [test results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0438/test-results/test/1629928589/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0438/test-artifacts/1629928589/windows-unittestfiles-openjdk11-1.15.0-build.0438.tgz]. > Command to copy region entries from a WAN site to another. > -- > > Key: GEODE-9369 > URL: https://issues.apache.org/jira/browse/GEODE-9369 > Project: Geode > Issue Type: New Feature > Components: wan >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > As described in RFC: > [https://cwiki.apache.org/confluence/display/GEODE/Geode+Command+to+replicate+region+data+from+one+site+to+another+connected+via+WAN] > it is proposed to implement a command that copies the entries of a region in > a WAN site to the same region in another WAN site by using WAN replication. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9464) Add a non-Steeltoe Asp.Net Core SessionState sample app to SessionStateCore
[
https://issues.apache.org/jira/browse/GEODE-9464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404771#comment-17404771
]
ASF GitHub Bot commented on GEODE-9464:
---
mmartell commented on a change in pull request #856:
URL: https://github.com/apache/geode-native/pull/856#discussion_r696178392
##
File path: netcore/AspNetCore GeodeSession Sample/Pages/Index.cshtml.cs
##
@@ -0,0 +1,71 @@
+using System;
+using Microsoft.AspNetCore.Http;
+using Microsoft.AspNetCore.Mvc;
+using Microsoft.AspNetCore.Mvc.RazorPages;
+using SessionSample.Middleware;
+using Web.Extensions;
+
+namespace SessionSample.Pages
+{
+public class IndexModel : PageModel
Review comment:
Good catch. I need to learn how to bulk clang-format a project.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscr...@geode.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Add a non-Steeltoe Asp.Net Core SessionState sample app to SessionStateCore
> ---
>
> Key: GEODE-9464
> URL: https://issues.apache.org/jira/browse/GEODE-9464
> Project: Geode
> Issue Type: Test
> Components: native client
>Reporter: Michael Martell
>Priority: Major
> Labels: pull-request-available
>
> The current Asp.Net sample app uses Steeltoe for discovery and registration
> of our sessionstate provider. We need a non-Steeltoe sample as well, since
> not everyone uses Steeltoe.
> This will be a good test of our NuGet access to the SessionState Core
> artifacts and its dependencies.
> Note: Ensure that the web application runs on all platforms.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-9552) ForcedDisconnectException is not handled in ExecutionHandlerContext
Donal Evans created GEODE-9552:
--
Summary: ForcedDisconnectException is not handled in
ExecutionHandlerContext
Key: GEODE-9552
URL: https://issues.apache.org/jira/browse/GEODE-9552
Project: Geode
Issue Type: Bug
Components: redis
Affects Versions: 1.15.0
Reporter: Donal Evans
As part of the changes in GEODE-9303, handling of various exceptions related to
function execution was removed from the
{{ExecutionHandlerContext.getExceptionResponse()}} method. However,
{{ForcedDisconnectException}} can still occur due to e.g. network partition,
and so handling for this exception should be restored.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9320) CI Failure: SetNXNativeRedisAcceptanceTest > classMethod FAILED
[
https://issues.apache.org/jira/browse/GEODE-9320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404768#comment-17404768
]
Dan Smith commented on GEODE-9320:
--
Note, the most recent failure was not a port conflict but this error message
{noformat}
org.junit.ComparisonFailure: [Incorrect primary node count] expected:<[3]> but
was:<[2]>
at
jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at
org.apache.geode.redis.NativeRedisClusterTestRule.waitForPrimaries(NativeRedisClusterTestRule.java:156)
at
org.apache.geode.redis.NativeRedisClusterTestRule.access$100(NativeRedisClusterTestRule.java:44)
at
org.apache.geode.redis.NativeRedisClusterTestRule$1.evaluate(NativeRedisClusterTestRule.java:91)
at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
at
org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:62)
at
org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:566)
at
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:36)
at
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at
org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:33)
at
org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:94)
at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
at
org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:119)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:566)
at
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:36)
at
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at
org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:182)
at
org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:164)
at
org.gradle.internal.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:414)
at
org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
at
org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at
org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:56)
at java.lang.Thread.run(Thread.java:829)
{noformat}
> CI Failure: SetNXNativeRedisAcceptanceTest > classMethod FAILED
> ---
>
> Key: GEODE-9320
> URL: https://issues.apache.org/jira/browse/GEODE-9320
> Project: Geode
> Issue Type: Bug
> Components: redis
>Reporter: Jens Deppe
>Priority: Major
> Labels: flaky-test
>
> {noformat}
>
[jira] [Commented] (GEODE-9464) Add a non-Steeltoe Asp.Net Core SessionState sample app to SessionStateCore
[
https://issues.apache.org/jira/browse/GEODE-9464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404766#comment-17404766
]
ASF GitHub Bot commented on GEODE-9464:
---
pivotal-jbarrett commented on a change in pull request #856:
URL: https://github.com/apache/geode-native/pull/856#discussion_r696171289
##
File path: netcore/AspNetCore GeodeSession Sample/Program.cs
##
@@ -0,0 +1,33 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+using Microsoft.AspNetCore;
+using Microsoft.AspNetCore.Hosting;
+
+namespace SessionSample
+{
+public class Program
Review comment:
Formatting
##
File path: netcore/AspNetCore GeodeSession Sample/Pages/Index.cshtml.cs
##
@@ -0,0 +1,71 @@
+using System;
+using Microsoft.AspNetCore.Http;
+using Microsoft.AspNetCore.Mvc;
+using Microsoft.AspNetCore.Mvc.RazorPages;
+using SessionSample.Middleware;
+using Web.Extensions;
+
+namespace SessionSample.Pages
+{
+public class IndexModel : PageModel
Review comment:
Formatting
##
File path: netcore/AspNetCore GeodeSession Sample/Startup.cs
##
@@ -0,0 +1,90 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+using Apache.Geode.Session;
+using Microsoft.AspNetCore.Builder;
+using Microsoft.AspNetCore.Hosting;
+using Microsoft.Extensions.Configuration;
+using Microsoft.Extensions.DependencyInjection;
+using Microsoft.Extensions.Logging;
+using Microsoft.Extensions.Hosting;
+using SessionSample.Middleware;
+using Microsoft.Extensions.Caching.Distributed;
+using System;
+
+namespace SessionSample
+{
+public class Startup
Review comment:
Formatting
##
File path: netcore/AspNetCore GeodeSession Sample/Properties/launchSettings.json
##
@@ -0,0 +1,28 @@
+{
+ "iisSettings": {
+"windowsAuthentication": false,
+"anonymousAuthentication": true,
+"iisExpress": {
+ "applicationUrl": "http://localhost:50795/;,
+ "sslPort": 44315
+}
+ },
+ "profiles": {
+"IIS Express": {
+ "commandName": "IISExpress",
+ "launchBrowser": true,
+ "environmentVariables": {
+"ASPNETCORE_ENVIRONMENT": "Development"
+ },
+ "nativeDebugging": true
+},
+"SessionSample": {
+ "commandName": "Project",
+ "launchBrowser": true,
+ "environmentVariables": {
+"ASPNETCORE_ENVIRONMENT": "Development"
+ },
+ "applicationUrl": "https://localhost:5001;http://localhost:5000;
+}
+ }
+}
Review comment:
New line
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscr...@geode.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Add a non-Steeltoe Asp.Net Core SessionState sample app to SessionStateCore
> ---
>
> Key: GEODE-9464
> URL: https://issues.apache.org/jira/browse/GEODE-9464
> Project: Geode
> Issue Type: Test
> Components: native client
>Reporter: Michael Martell
>Priority: Major
> Labels: pull-request-available
>
> The current Asp.Net sample app uses Steeltoe for discovery and registration
> of our
[jira] [Updated] (GEODE-8719) CI Failure: org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest > givenServerCrashesDuringAPPEND_thenDataIsNotLost
[
https://issues.apache.org/jira/browse/GEODE-8719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith updated GEODE-8719:
-
Fix Version/s: 1.15.0
> CI Failure:
> org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest >
> givenServerCrashesDuringAPPEND_thenDataIsNotLost
> -
>
> Key: GEODE-8719
> URL: https://issues.apache.org/jira/browse/GEODE-8719
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.14.0, 1.15.0
>Reporter: Sarah Abbey
>Assignee: Jens Deppe
>Priority: Minor
> Labels: flaky-test
> Fix For: 1.15.0
>
>
> CI failure: https://concourse.apachegeode-ci.info/builds/207449
> {code:java}
> org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest >
> givenServerCrashesDuringAPPEND_thenDataIsNotLost FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.test.dunit.internal.IdentifiableCallable.call in VM 2
> running on Host e0e2f6af9445 with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:623)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:460)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:268)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:261)
> at
> org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest.startRedisVM(CrashAndNoRepeatDUnitTest.java:131)
> at
> org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest.givenServerCrashesDuringAPPEND_thenDataIsNotLost(CrashAndNoRepeatDUnitTest.java:164)
> Caused by:
> org.apache.geode.management.ManagementException: Could not start
> Redis Server using bind address: localhost/127.0.0.1 and port: 44579. Please
> make sure nothing else is running on this address/port combination.
> Caused by:
> java.net.BindException: Address already in use
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-8719) CI Failure: org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest > givenServerCrashesDuringAPPEND_thenDataIsNotLost
[
https://issues.apache.org/jira/browse/GEODE-8719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith resolved GEODE-8719.
--
Resolution: Won't Fix
This test was deleted a while ago as part of
198f66489d842994abbcbabd621c3ed6f4d8c730. Closing this ticket.
> CI Failure:
> org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest >
> givenServerCrashesDuringAPPEND_thenDataIsNotLost
> -
>
> Key: GEODE-8719
> URL: https://issues.apache.org/jira/browse/GEODE-8719
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.14.0, 1.15.0
>Reporter: Sarah Abbey
>Assignee: Jens Deppe
>Priority: Minor
> Labels: flaky-test
>
> CI failure: https://concourse.apachegeode-ci.info/builds/207449
> {code:java}
> org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest >
> givenServerCrashesDuringAPPEND_thenDataIsNotLost FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.test.dunit.internal.IdentifiableCallable.call in VM 2
> running on Host e0e2f6af9445 with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:623)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:460)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:268)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.startServerVM(ClusterStartupRule.java:261)
> at
> org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest.startRedisVM(CrashAndNoRepeatDUnitTest.java:131)
> at
> org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest.givenServerCrashesDuringAPPEND_thenDataIsNotLost(CrashAndNoRepeatDUnitTest.java:164)
> Caused by:
> org.apache.geode.management.ManagementException: Could not start
> Redis Server using bind address: localhost/127.0.0.1 and port: 44579. Please
> make sure nothing else is running on this address/port combination.
> Caused by:
> java.net.BindException: Address already in use
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9509) CI Failure: RedisPartitionResolverDUnitTest fails with suspect strings
[
https://issues.apache.org/jira/browse/GEODE-9509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith updated GEODE-9509:
-
Fix Version/s: 1.15.0
> CI Failure: RedisPartitionResolverDUnitTest fails with suspect strings
> --
>
> Key: GEODE-9509
> URL: https://issues.apache.org/jira/browse/GEODE-9509
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Priority: Major
> Fix For: 1.15.0
>
>
> {noformat}
> org.apache.geode.redis.internal.cluster.RedisPartitionResolverDUnitTest >
> classMethod 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 713
> [fatal 2021/08/14 18:02:15.696 UTC tid=57]
> Exception in processing request from 10.0.0.113
> java.lang.Exception: Improperly configured client detected - use
> addPoolLocator to configure its locators instead of addPoolServer.
> at
> org.apache.geode.distributed.internal.ProtocolCheckerImpl.checkProtocol(ProtocolCheckerImpl.java:31)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:342)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> ---
> Found suspect string in 'dunit_suspect-vm0.log' at line 777
> [fatal 2021/08/14 18:02:28.025 UTC tid=57]
> Exception in processing request from 10.0.0.113
> java.lang.Exception: Improperly configured client detected - use
> addPoolLocator to configure its locators instead of addPoolServer.
> at
> org.apache.geode.distributed.internal.ProtocolCheckerImpl.checkProtocol(ProtocolCheckerImpl.java:31)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:342)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> ---
> Found suspect string in 'dunit_suspect-vm0.log' at line 785
> [fatal 2021/08/14 18:02:28.028 UTC tid=57]
> Exception in processing request from 10.0.0.113
> java.lang.Exception: Improperly configured client detected - use
> addPoolLocator to configure its locators instead of addPoolServer.
> at
> org.apache.geode.distributed.internal.ProtocolCheckerImpl.checkProtocol(ProtocolCheckerImpl.java:31)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:342)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> ---
> Found suspect string in 'dunit_suspect-vm0.log' at line 793
> [fatal 2021/08/14 18:02:28.064 UTC tid=57]
> Exception in processing request from 10.0.0.113
> java.lang.Exception: Improperly configured client detected - use
> addPoolLocator to configure its locators instead of addPoolServer.
> at
> org.apache.geode.distributed.internal.ProtocolCheckerImpl.checkProtocol(ProtocolCheckerImpl.java:31)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:342)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Hit occurrence limit of 5 for this string.
> Further reporting of this type of error will be suppressed.
> at org.junit.Assert.fail(Assert.java:89)
> at
> org.apache.geode.test.dunit.internal.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:409)
> at
> org.apache.geode.test.dunit.internal.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:425)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.after(ClusterStartupRule.java:186)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.access$100(ClusterStartupRule.java:70)
>
[jira] [Resolved] (GEODE-9509) CI Failure: RedisPartitionResolverDUnitTest fails with suspect strings
[
https://issues.apache.org/jira/browse/GEODE-9509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith resolved GEODE-9509.
--
Resolution: Duplicate
This is a duplicate of GEODE-9537. I double checked the progress files, as Jens
suggested, and I see that CqDataUsingPoolOptimizedExecuteDUnitTest was running
at the same time, which will cause this "Improperly configured client" error
message.
> CI Failure: RedisPartitionResolverDUnitTest fails with suspect strings
> --
>
> Key: GEODE-9509
> URL: https://issues.apache.org/jira/browse/GEODE-9509
> Project: Geode
> Issue Type: Bug
> Components: redis
>Affects Versions: 1.15.0
>Reporter: Donal Evans
>Priority: Major
>
> {noformat}
> org.apache.geode.redis.internal.cluster.RedisPartitionResolverDUnitTest >
> classMethod 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 713
> [fatal 2021/08/14 18:02:15.696 UTC tid=57]
> Exception in processing request from 10.0.0.113
> java.lang.Exception: Improperly configured client detected - use
> addPoolLocator to configure its locators instead of addPoolServer.
> at
> org.apache.geode.distributed.internal.ProtocolCheckerImpl.checkProtocol(ProtocolCheckerImpl.java:31)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:342)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> ---
> Found suspect string in 'dunit_suspect-vm0.log' at line 777
> [fatal 2021/08/14 18:02:28.025 UTC tid=57]
> Exception in processing request from 10.0.0.113
> java.lang.Exception: Improperly configured client detected - use
> addPoolLocator to configure its locators instead of addPoolServer.
> at
> org.apache.geode.distributed.internal.ProtocolCheckerImpl.checkProtocol(ProtocolCheckerImpl.java:31)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:342)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> ---
> Found suspect string in 'dunit_suspect-vm0.log' at line 785
> [fatal 2021/08/14 18:02:28.028 UTC tid=57]
> Exception in processing request from 10.0.0.113
> java.lang.Exception: Improperly configured client detected - use
> addPoolLocator to configure its locators instead of addPoolServer.
> at
> org.apache.geode.distributed.internal.ProtocolCheckerImpl.checkProtocol(ProtocolCheckerImpl.java:31)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:342)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> ---
> Found suspect string in 'dunit_suspect-vm0.log' at line 793
> [fatal 2021/08/14 18:02:28.064 UTC tid=57]
> Exception in processing request from 10.0.0.113
> java.lang.Exception: Improperly configured client detected - use
> addPoolLocator to configure its locators instead of addPoolServer.
> at
> org.apache.geode.distributed.internal.ProtocolCheckerImpl.checkProtocol(ProtocolCheckerImpl.java:31)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:342)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Hit occurrence limit of 5 for this string.
> Further reporting of this type of error will be suppressed.
> at org.junit.Assert.fail(Assert.java:89)
> at
> org.apache.geode.test.dunit.internal.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:409)
> at
> org.apache.geode.test.dunit.internal.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:425)
[jira] [Resolved] (GEODE-9319) CI failure: session.NativeRedisSessionExpirationAcceptanceTest > classMethod FAILED
[
https://issues.apache.org/jira/browse/GEODE-9319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith resolved GEODE-9319.
--
Fix Version/s: 1.15.0
Resolution: Duplicate
Resolving this as a duplicate of GEODE-9490. This is the same suspect string
from the RedisProxy, which will now be ignored after with the fix for
GEODE-9490.
> CI failure: session.NativeRedisSessionExpirationAcceptanceTest > classMethod
> FAILED
> ---
>
> Key: GEODE-9319
> URL: https://issues.apache.org/jira/browse/GEODE-9319
> Project: Geode
> Issue Type: Bug
> Components: redis
>Reporter: Jens Deppe
>Priority: Major
> Labels: flaky-test
> Fix For: 1.15.0
>
>
> {noformat}
> session.NativeRedisSessionExpirationAcceptanceTest > classMethod FAILED
> 14:17:23java.lang.AssertionError: Suspicious strings were written to the
> log during this run.
> 14:17:23Fix the strings or use IgnoredException.addIgnoredException to
> ignore.
> 14:17:23
> ---
> 14:17:23Found suspect string in 'dunit_suspect-local.log' at line 287
> 14:17:23
> 14:17:23[error 2021/05/26 21:17:10.762 UTC tid=92]
> Failed to return response on inboundChannel
> 14:17:23io.netty.channel.StacklessClosedChannelException
> 14:17:23 at
> io.netty.channel.AbstractChannel$AbstractUnsafe.write(Object,
> ChannelPromise)(Unknown Source)
> 14:17:23at org.junit.Assert.fail(Assert.java:89)
> 14:17:23at
> org.apache.geode.test.dunit.internal.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:409)
> 14:17:23at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.after(ClusterStartupRule.java:185)
> 14:17:23at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.access$100(ClusterStartupRule.java:69)
> 14:17:23at
> org.apache.geode.test.dunit.rules.ClusterStartupRule$1.evaluate(ClusterStartupRule.java:140)
> 14:17:23at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> 14:17:23at
> org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> 14:17:23at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> 14:17:23at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110)
> 14:17:23at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
> 14:17:23at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
> 14:17:23at
> org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:62)
> 14:17:23at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
> 14:17:23at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 14:17:23at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 14:17:23at
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 14:17:23at java.lang.reflect.Method.invoke(Method.java:566)
> 14:17:23at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:36)
> 14:17:23at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> 14:17:23at
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:33)
> 14:17:23at
> org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:94)
> 14:17:23at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> 14:17:23at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:119)
> 14:17:23at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 14:17:23at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 14:17:23at
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 14:17:23at java.lang.reflect.Method.invoke(Method.java:566)
> 14:17:23at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:36)
> 14:17:23at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> 14:17:23at
> org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:182)
> 14:17:23at
>
[jira] [Updated] (GEODE-9546) Enable Redis Server to Authenticate Using SecurityManager
[ https://issues.apache.org/jira/browse/GEODE-9546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wayne updated GEODE-9546: - Description: The Redis [AUTH|https://redis.io/commands/auth] command must be integrated with the Geode SecurityManager. # Remove the Geode property compatible-with-redis-password that currently being used for the Redis password. # Add a new geode property for the Redis default user ID, compatible-with-redis-username # When a user issues an AUTH Command, the server must call the authenticate method on the customer's SecurityManager with the user (security-username property) and the user provided password (security-password property) and properly handle the AuthenticationFailedException. If the AUTH command was called without a user the value of compatible-with-redis-user should be used** # The Object/Principal returned from a successful authenticate method call must be cached, associated with the client connection, and available for reuse in subsequent authorization calls. **When the AUTH command has a single argument (e.g. AUTH xx) the single argument is interpreted as a password/token and the default Redis user is used for authentication. When the AUTH command has two arguments (e.g. AUTH xx yy) the first argument is interpreted as a username and is used instead of the default Redis user. The second argument is interpreted as a password. +Acceptance Criteria+ When a SecurityManager is configured, Redis clients that don't AUTH with a valid password cannot perform operations. Redis clients that do AUTH with a valid password can perform Redis operations. Until we support ACLS, use of the AUTH command with more than two arguments is invalid syntax. was: The Redis [AUTH|https://redis.io/commands/auth] command must be integrated with the Geode SecurityManager. # Remove the Geode property compatible-with-redis-password that currently being used for the Redis password. # Add a new geode property for the Redis default user ID, compatible-with-redis-username # When a user issues an AUTH Command, the server must call the authenticate method on the customer's SecurityManager with the user (security-username property) and the user provided password (security-password property) and properly handle the AuthenticationFailedException. If the AUTH command was called without a user the value of compatible-with-redis-user should be used** # The Object/Principal returned from a successful authenticate method call must be cached, associated with the client connection, and available for reuse in subsequent authorization calls. **When the AUTH command has a single argument (e.g. AUTH xx) the single argument is interpreted as a password/token and the default Redis user is used for authentication. When the AUTH command has two arguments (e.g. AUTH xx yy) the first argument is interpreted as a username and is used instead of the default Redis user. The second argument is interpreted as a password. +Acceptance Criteria+ When a SecurityManager is configured, Redis clients that don't AUTH with a valid password cannot perform operations. Redis clients that do AUTH with a valid password can perform Redis operations. Until we support ACLS. Use of the AUTH command with more than two arguments is invalid syntax. > Enable Redis Server to Authenticate Using SecurityManager > - > > Key: GEODE-9546 > URL: https://issues.apache.org/jira/browse/GEODE-9546 > Project: Geode > Issue Type: New Feature >Reporter: Wayne >Priority: Major > > The Redis [AUTH|https://redis.io/commands/auth] command must be integrated > with the Geode SecurityManager. > # Remove the Geode property compatible-with-redis-password that currently > being used for the Redis password. > # Add a new geode property for the Redis default user ID, > compatible-with-redis-username > # When a user issues an AUTH Command, the server must call the authenticate > method on the customer's SecurityManager with the user (security-username > property) and the user provided password (security-password property) and > properly handle the AuthenticationFailedException. If the AUTH command was > called without a user the value of compatible-with-redis-user should be used** > # The Object/Principal returned from a successful authenticate method call > must be cached, associated with the client connection, and available for > reuse in subsequent authorization calls. > **When the AUTH command has a single argument (e.g. AUTH xx) the single > argument is interpreted as a password/token and the default Redis user is > used for authentication. When the AUTH command has two arguments (e.g. AUTH > xx yy) the first argument is interpreted as a username and
[jira] [Assigned] (GEODE-9551) New SNI proxy API does not conform to standards.
[
https://issues.apache.org/jira/browse/GEODE-9551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacob Barrett reassigned GEODE-9551:
Assignee: Jacob Barrett
> New SNI proxy API does not conform to standards.
>
>
> Key: GEODE-9551
> URL: https://issues.apache.org/jira/browse/GEODE-9551
> Project: Geode
> Issue Type: Bug
> Components: native client
>Affects Versions: 1.14.0, 1.15.0
>Reporter: Jacob Barrett
>Assignee: Jacob Barrett
>Priority: Major
>
> APIs should be consistent with other APIs:
> All class/struct properties should be returned {{const &}} in getters and
> copied in setters.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9453) The server, once a user expires, should clean the user attributes from the server.
[ https://issues.apache.org/jira/browse/GEODE-9453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-9453: -- Labels: GeodeOperationAPI pull-request-available (was: GeodeOperationAPI) > The server, once a user expires, should clean the user attributes from the > server. > -- > > Key: GEODE-9453 > URL: https://issues.apache.org/jira/browse/GEODE-9453 > Project: Geode > Issue Type: Sub-task > Components: core, security >Reporter: Jinmei Liao >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > > ClientUserAuths maintains a map of clientID to its user attributes (the > logged in shiro subject etc), when user expires, we need to remove that entry > from that map and log the shiro subject out to avoid resource leak. > make sure to include tests in multi-server cases -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9550) Native Client user guide: warn against floating point values in keys
[ https://issues.apache.org/jira/browse/GEODE-9550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-9550. Fix Version/s: 1.12.4 1.13.4 1.15.0 1.14.0 Resolution: Fixed > Native Client user guide: warn against floating point values in keys > > > Key: GEODE-9550 > URL: https://issues.apache.org/jira/browse/GEODE-9550 > Project: Geode > Issue Type: Improvement > Components: docs, native client >Affects Versions: 1.13.4 >Reporter: Dave Barnes >Priority: Major > Labels: pull-request-available > Fix For: 1.14.0, 1.15.0, 1.13.4, 1.12.4 > > > Request from a community member: > You should NEVER use a floating point value as a key, or key component, but > for some reason we allow it. > Since this can't be prevented in code, warn against this practice in the docs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9550) Native Client user guide: warn against floating point values in keys
[ https://issues.apache.org/jira/browse/GEODE-9550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404731#comment-17404731 ] ASF subversion and git services commented on GEODE-9550: Commit 8386624c9acdcece729c370f007496262fc65d65 in geode-native's branch refs/heads/develop from Dave Barnes [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=8386624 ] GEODE-9550: Native Client user guide: warn against floating point values in keys (#857) (#859) > Native Client user guide: warn against floating point values in keys > > > Key: GEODE-9550 > URL: https://issues.apache.org/jira/browse/GEODE-9550 > Project: Geode > Issue Type: Improvement > Components: docs, native client >Affects Versions: 1.13.4 >Reporter: Dave Barnes >Priority: Major > Labels: pull-request-available > > Request from a community member: > You should NEVER use a floating point value as a key, or key component, but > for some reason we allow it. > Since this can't be prevented in code, warn against this practice in the docs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9550) Native Client user guide: warn against floating point values in keys
[ https://issues.apache.org/jira/browse/GEODE-9550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404730#comment-17404730 ] ASF GitHub Bot commented on GEODE-9550: --- davebarnes97 merged pull request #859: URL: https://github.com/apache/geode-native/pull/859 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@geode.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Native Client user guide: warn against floating point values in keys > > > Key: GEODE-9550 > URL: https://issues.apache.org/jira/browse/GEODE-9550 > Project: Geode > Issue Type: Improvement > Components: docs, native client >Affects Versions: 1.13.4 >Reporter: Dave Barnes >Priority: Major > Labels: pull-request-available > > Request from a community member: > You should NEVER use a floating point value as a key, or key component, but > for some reason we allow it. > Since this can't be prevented in code, warn against this practice in the docs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9452) The older version client should receive the AuthenticationRequiredException when authentication expires
[ https://issues.apache.org/jira/browse/GEODE-9452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404727#comment-17404727 ] ASF subversion and git services commented on GEODE-9452: Commit b944ace9c4714dd87037de6726154c9b8c1fb7d9 in geode's branch refs/heads/develop from Jinmei Liao [ https://gitbox.apache.org/repos/asf?p=geode.git;h=b944ace ] GEODE-9451: On demand authentication expiration and re-authentication (#6787) * GEODE-9456, GEODE-9452: Authentication Expiration (#6721) * Add tests and throw AuthenticationExpiredException * GEODE-9460: Add testing for mutli-user scenarios (#6755) Co-authored-by: Joris Melchior > The older version client should receive the AuthenticationRequiredException > when authentication expires > --- > > Key: GEODE-9452 > URL: https://issues.apache.org/jira/browse/GEODE-9452 > Project: Geode > Issue Type: Sub-task > Components: core, security >Reporter: Jinmei Liao >Assignee: Jinmei Liao >Priority: Major > Labels: GeodeOperationAPI > > Currently, for older client, it's receiving a ClassNotFoundException, we need > to add the serialization code to convert the AuthenticationExpiredException > into this old exception type that the older clients can understand. > > Note: when converting the exception, if we have the message to match what the > older client expects, it can do re-authentication automatically, but we lost > the original message that server has thrown. (Need to consult the PM on what > kind of behavior they want). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9460) add tests for multi-user mode when one user expires
[ https://issues.apache.org/jira/browse/GEODE-9460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404728#comment-17404728 ] ASF subversion and git services commented on GEODE-9460: Commit b944ace9c4714dd87037de6726154c9b8c1fb7d9 in geode's branch refs/heads/develop from Jinmei Liao [ https://gitbox.apache.org/repos/asf?p=geode.git;h=b944ace ] GEODE-9451: On demand authentication expiration and re-authentication (#6787) * GEODE-9456, GEODE-9452: Authentication Expiration (#6721) * Add tests and throw AuthenticationExpiredException * GEODE-9460: Add testing for mutli-user scenarios (#6755) Co-authored-by: Joris Melchior > 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-9551) New SNI proxy API does not conform to standards.
Jacob Barrett created GEODE-9551:
Summary: New SNI proxy API does not conform to standards.
Key: GEODE-9551
URL: https://issues.apache.org/jira/browse/GEODE-9551
Project: Geode
Issue Type: Bug
Components: native client
Affects Versions: 1.14.0, 1.15.0
Reporter: Jacob Barrett
APIs should be consistent with other APIs:
All class/struct properties should be returned {{const &}} in getters and
copied in setters.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9456) Create AuthenticationExpiredException and have the client handle that exception for re-authentication
[ https://issues.apache.org/jira/browse/GEODE-9456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404726#comment-17404726 ] ASF subversion and git services commented on GEODE-9456: Commit b944ace9c4714dd87037de6726154c9b8c1fb7d9 in geode's branch refs/heads/develop from Jinmei Liao [ https://gitbox.apache.org/repos/asf?p=geode.git;h=b944ace ] GEODE-9451: On demand authentication expiration and re-authentication (#6787) * GEODE-9456, GEODE-9452: Authentication Expiration (#6721) * Add tests and throw AuthenticationExpiredException * GEODE-9460: Add testing for mutli-user scenarios (#6755) Co-authored-by: Joris Melchior > Create AuthenticationExpiredException and have the client handle that > exception for re-authentication > - > > Key: GEODE-9456 > URL: https://issues.apache.org/jira/browse/GEODE-9456 > Project: Geode > Issue Type: Sub-task > Components: core, security >Reporter: Jinmei Liao >Assignee: Jinmei Liao >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > > Create AuthenticationExpiredException and have the client handle that > exception for re-authentication > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9451) On demand authentication expiration and re-authentication
[ https://issues.apache.org/jira/browse/GEODE-9451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404725#comment-17404725 ] ASF subversion and git services commented on GEODE-9451: Commit b944ace9c4714dd87037de6726154c9b8c1fb7d9 in geode's branch refs/heads/develop from Jinmei Liao [ https://gitbox.apache.org/repos/asf?p=geode.git;h=b944ace ] GEODE-9451: On demand authentication expiration and re-authentication (#6787) * GEODE-9456, GEODE-9452: Authentication Expiration (#6721) * Add tests and throw AuthenticationExpiredException * GEODE-9460: Add testing for mutli-user scenarios (#6755) Co-authored-by: Joris Melchior > On demand authentication expiration and re-authentication > - > > Key: GEODE-9451 > URL: https://issues.apache.org/jira/browse/GEODE-9451 > Project: Geode > Issue Type: New Feature > Components: core, security >Reporter: Jinmei Liao >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9550) Native Client user guide: warn against floating point values in keys
[ https://issues.apache.org/jira/browse/GEODE-9550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404720#comment-17404720 ] ASF subversion and git services commented on GEODE-9550: Commit 3a7b8128656a4a573eef6dba9fb4cc8ce0bcc821 in geode-native's branch refs/heads/support/1.12 from Dave Barnes [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=3a7b812 ] GEODE-9550: Native Client user guide: warn against floating point values in keys (#857) * GEODE-9550: Native Client user guide: warn against floating point values in keys > Native Client user guide: warn against floating point values in keys > > > Key: GEODE-9550 > URL: https://issues.apache.org/jira/browse/GEODE-9550 > Project: Geode > Issue Type: Improvement > Components: docs, native client >Affects Versions: 1.13.4 >Reporter: Dave Barnes >Priority: Major > Labels: pull-request-available > > Request from a community member: > You should NEVER use a floating point value as a key, or key component, but > for some reason we allow it. > Since this can't be prevented in code, warn against this practice in the docs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9550) Native Client user guide: warn against floating point values in keys
[ https://issues.apache.org/jira/browse/GEODE-9550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404721#comment-17404721 ] ASF subversion and git services commented on GEODE-9550: Commit 3a7b8128656a4a573eef6dba9fb4cc8ce0bcc821 in geode-native's branch refs/heads/support/1.12 from Dave Barnes [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=3a7b812 ] GEODE-9550: Native Client user guide: warn against floating point values in keys (#857) * GEODE-9550: Native Client user guide: warn against floating point values in keys > Native Client user guide: warn against floating point values in keys > > > Key: GEODE-9550 > URL: https://issues.apache.org/jira/browse/GEODE-9550 > Project: Geode > Issue Type: Improvement > Components: docs, native client >Affects Versions: 1.13.4 >Reporter: Dave Barnes >Priority: Major > Labels: pull-request-available > > Request from a community member: > You should NEVER use a floating point value as a key, or key component, but > for some reason we allow it. > Since this can't be prevented in code, warn against this practice in the docs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9550) Native Client user guide: warn against floating point values in keys
[ https://issues.apache.org/jira/browse/GEODE-9550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404718#comment-17404718 ] ASF subversion and git services commented on GEODE-9550: Commit 1c765f745485d92f9a49e1ada3772a5bb69d67bf in geode-native's branch refs/heads/support/1.13 from Dave Barnes [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=1c765f7 ] GEODE-9550: Native Client user guide: warn against floating point values in keys (#857) * GEODE-9550: Native Client user guide: warn against floating point values in keys > Native Client user guide: warn against floating point values in keys > > > Key: GEODE-9550 > URL: https://issues.apache.org/jira/browse/GEODE-9550 > Project: Geode > Issue Type: Improvement > Components: docs, native client >Affects Versions: 1.13.4 >Reporter: Dave Barnes >Priority: Major > Labels: pull-request-available > > Request from a community member: > You should NEVER use a floating point value as a key, or key component, but > for some reason we allow it. > Since this can't be prevented in code, warn against this practice in the docs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9550) Native Client user guide: warn against floating point values in keys
[ https://issues.apache.org/jira/browse/GEODE-9550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404719#comment-17404719 ] ASF subversion and git services commented on GEODE-9550: Commit 1c765f745485d92f9a49e1ada3772a5bb69d67bf in geode-native's branch refs/heads/support/1.13 from Dave Barnes [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=1c765f7 ] GEODE-9550: Native Client user guide: warn against floating point values in keys (#857) * GEODE-9550: Native Client user guide: warn against floating point values in keys > Native Client user guide: warn against floating point values in keys > > > Key: GEODE-9550 > URL: https://issues.apache.org/jira/browse/GEODE-9550 > Project: Geode > Issue Type: Improvement > Components: docs, native client >Affects Versions: 1.13.4 >Reporter: Dave Barnes >Priority: Major > Labels: pull-request-available > > Request from a community member: > You should NEVER use a floating point value as a key, or key component, but > for some reason we allow it. > Since this can't be prevented in code, warn against this practice in the docs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9550) Native Client user guide: warn against floating point values in keys
[ https://issues.apache.org/jira/browse/GEODE-9550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404717#comment-17404717 ] ASF GitHub Bot commented on GEODE-9550: --- davebarnes97 merged pull request #857: URL: https://github.com/apache/geode-native/pull/857 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@geode.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Native Client user guide: warn against floating point values in keys > > > Key: GEODE-9550 > URL: https://issues.apache.org/jira/browse/GEODE-9550 > Project: Geode > Issue Type: Improvement > Components: docs, native client >Affects Versions: 1.13.4 >Reporter: Dave Barnes >Priority: Major > > Request from a community member: > You should NEVER use a floating point value as a key, or key component, but > for some reason we allow it. > Since this can't be prevented in code, warn against this practice in the docs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9550) Native Client user guide: warn against floating point values in keys
[ https://issues.apache.org/jira/browse/GEODE-9550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404716#comment-17404716 ] ASF subversion and git services commented on GEODE-9550: Commit 064c43f7e0b0220a11a2c6d47549db4fc01c7d95 in geode-native's branch refs/heads/support/1.14 from Dave Barnes [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=064c43f ] GEODE-9550: Native Client user guide: warn against floating point values in keys (#857) * GEODE-9550: Native Client user guide: warn against floating point values in keys > Native Client user guide: warn against floating point values in keys > > > Key: GEODE-9550 > URL: https://issues.apache.org/jira/browse/GEODE-9550 > Project: Geode > Issue Type: Improvement > Components: docs, native client >Affects Versions: 1.13.4 >Reporter: Dave Barnes >Priority: Major > > Request from a community member: > You should NEVER use a floating point value as a key, or key component, but > for some reason we allow it. > Since this can't be prevented in code, warn against this practice in the docs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9550) Native Client user guide: warn against floating point values in keys
[ https://issues.apache.org/jira/browse/GEODE-9550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-9550: -- Labels: pull-request-available (was: ) > Native Client user guide: warn against floating point values in keys > > > Key: GEODE-9550 > URL: https://issues.apache.org/jira/browse/GEODE-9550 > Project: Geode > Issue Type: Improvement > Components: docs, native client >Affects Versions: 1.13.4 >Reporter: Dave Barnes >Priority: Major > Labels: pull-request-available > > Request from a community member: > You should NEVER use a floating point value as a key, or key component, but > for some reason we allow it. > Since this can't be prevented in code, warn against this practice in the docs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9550) Native Client user guide: warn against floating point values in keys
[ https://issues.apache.org/jira/browse/GEODE-9550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404715#comment-17404715 ] ASF subversion and git services commented on GEODE-9550: Commit 064c43f7e0b0220a11a2c6d47549db4fc01c7d95 in geode-native's branch refs/heads/support/1.14 from Dave Barnes [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=064c43f ] GEODE-9550: Native Client user guide: warn against floating point values in keys (#857) * GEODE-9550: Native Client user guide: warn against floating point values in keys > Native Client user guide: warn against floating point values in keys > > > Key: GEODE-9550 > URL: https://issues.apache.org/jira/browse/GEODE-9550 > Project: Geode > Issue Type: Improvement > Components: docs, native client >Affects Versions: 1.13.4 >Reporter: Dave Barnes >Priority: Major > > Request from a community member: > You should NEVER use a floating point value as a key, or key component, but > for some reason we allow it. > Since this can't be prevented in code, warn against this practice in the docs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9528) CI Failure: DistributionAdvisorIntegrationTest > verifyMembershipListenerIsRemovedAfterForceDisconnect
[
https://issues.apache.org/jira/browse/GEODE-9528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404706#comment-17404706
]
ASF subversion and git services commented on GEODE-9528:
Commit ed816c55406131b95d4db8571558ed1fcecc53e7 in geode's branch
refs/heads/develop from Barry Oglesby
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=ed816c5 ]
GEODE-9528: Updated test to await until asserted (#6798)
> CI Failure: DistributionAdvisorIntegrationTest >
> verifyMembershipListenerIsRemovedAfterForceDisconnect
> --
>
> Key: GEODE-9528
> URL: https://issues.apache.org/jira/browse/GEODE-9528
> Project: Geode
> Issue Type: Bug
> Components: membership
>Affects Versions: 1.12.5, 1.13.5, 1.14.0
>Reporter: Owen Nichols
>Assignee: Barrett Oglesby
>Priority: Major
> Labels: pull-request-available
>
> {noformat}
> org.apache.geode.distributed.internal.DistributionAdvisorIntegrationTest >
> verifyMembershipListenerIsRemovedAfterForceDisconnect FAILED
> org.junit.ComparisonFailure: expected:<[fals]e> but was:<[tru]e>
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.distributed.internal.DistributionAdvisorIntegrationTest.verifyMembershipListenerIsRemovedAfterForceDisconnect(DistributionAdvisorIntegrationTest.java:57)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9464) Add a non-Steeltoe Asp.Net Core SessionState sample app to SessionStateCore
[
https://issues.apache.org/jira/browse/GEODE-9464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404702#comment-17404702
]
ASF GitHub Bot commented on GEODE-9464:
---
mmartell commented on a change in pull request #856:
URL: https://github.com/apache/geode-native/pull/856#discussion_r696091053
##
File path: netcore/geode-dotnet-core.sln
##
@@ -13,35 +13,70 @@ Project("{9A19103F-16F7-4668-BE54-9A1E7A4F7556}") =
"NetCore.Session", "NetCore.
EndProject
Project("{9A19103F-16F7-4668-BE54-9A1E7A4F7556}") =
"NetCore.Session.IntegrationTests",
"NetCore.Session.IntegrationTests\NetCore.Session.IntegrationTests.csproj",
"{94D2CD59-A5F3-4504-BF01-0A3B95CE12B5}"
EndProject
+Project("{9A19103F-16F7-4668-BE54-9A1E7A4F7556}") = "AspNetCore GeodeSession
Sample", "AspNetCore GeodeSession Sample\AspNetCore GeodeSession
Sample.csproj", "{4E830BC8-D1CA-40AF-9C9C-D15E193C6585}"
+EndProject
Global
GlobalSection(SolutionConfigurationPlatforms) = preSolution
+ Debug|Any CPU = Debug|Any CPU
Debug|x64 = Debug|x64
+ Debug|x86 = Debug|x86
+ Release|Any CPU = Release|Any CPU
Release|x64 = Release|x64
+ Release|x86 = Release|x86
EndGlobalSection
GlobalSection(ProjectConfigurationPlatforms) = postSolution
+ {09ABBCE7-B217-43F1-A51B-CC5BDCD8EE98}.Debug|Any CPU.ActiveCfg
= Debug|x64
{09ABBCE7-B217-43F1-A51B-CC5BDCD8EE98}.Debug|x64.ActiveCfg =
Debug|x64
{09ABBCE7-B217-43F1-A51B-CC5BDCD8EE98}.Debug|x64.Build.0 =
Debug|x64
+ {09ABBCE7-B217-43F1-A51B-CC5BDCD8EE98}.Debug|x86.ActiveCfg =
Debug|x64
+ {09ABBCE7-B217-43F1-A51B-CC5BDCD8EE98}.Release|Any
CPU.ActiveCfg = Release|x64
{09ABBCE7-B217-43F1-A51B-CC5BDCD8EE98}.Release|x64.ActiveCfg =
Release|x64
{09ABBCE7-B217-43F1-A51B-CC5BDCD8EE98}.Release|x64.Build.0 =
Release|x64
+ {09ABBCE7-B217-43F1-A51B-CC5BDCD8EE98}.Release|x86.ActiveCfg =
Release|x64
+ {501DEA7E-8985-42A8-8BC9-C073E1B6DFE0}.Debug|Any CPU.ActiveCfg
= Debug|x64
{501DEA7E-8985-42A8-8BC9-C073E1B6DFE0}.Debug|x64.ActiveCfg =
Debug|x64
{501DEA7E-8985-42A8-8BC9-C073E1B6DFE0}.Debug|x64.Build.0 =
Debug|x64
+ {501DEA7E-8985-42A8-8BC9-C073E1B6DFE0}.Debug|x86.ActiveCfg =
Debug|x64
+ {501DEA7E-8985-42A8-8BC9-C073E1B6DFE0}.Release|Any
CPU.ActiveCfg = Release|x64
{501DEA7E-8985-42A8-8BC9-C073E1B6DFE0}.Release|x64.ActiveCfg =
Release|x64
{501DEA7E-8985-42A8-8BC9-C073E1B6DFE0}.Release|x64.Build.0 =
Release|x64
+ {501DEA7E-8985-42A8-8BC9-C073E1B6DFE0}.Release|x86.ActiveCfg =
Release|x64
+ {B88C58EB-B144-403B-85F7-7A5B45E643E3}.Debug|Any CPU.ActiveCfg
= Debug|x64
{B88C58EB-B144-403B-85F7-7A5B45E643E3}.Debug|x64.ActiveCfg =
Debug|x64
{B88C58EB-B144-403B-85F7-7A5B45E643E3}.Debug|x64.Build.0 =
Debug|x64
+ {B88C58EB-B144-403B-85F7-7A5B45E643E3}.Debug|x86.ActiveCfg =
Debug|x64
+ {B88C58EB-B144-403B-85F7-7A5B45E643E3}.Release|Any
CPU.ActiveCfg = Release|x64
{B88C58EB-B144-403B-85F7-7A5B45E643E3}.Release|x64.ActiveCfg =
Release|x64
{B88C58EB-B144-403B-85F7-7A5B45E643E3}.Release|x64.Build.0 =
Release|x64
+ {B88C58EB-B144-403B-85F7-7A5B45E643E3}.Release|x86.ActiveCfg =
Release|x64
+ {94D2CD59-A5F3-4504-BF01-0A3B95CE12B5}.Debug|Any CPU.ActiveCfg
= Debug|x64
{94D2CD59-A5F3-4504-BF01-0A3B95CE12B5}.Debug|x64.ActiveCfg =
Debug|x64
{94D2CD59-A5F3-4504-BF01-0A3B95CE12B5}.Debug|x64.Build.0 =
Debug|x64
+ {94D2CD59-A5F3-4504-BF01-0A3B95CE12B5}.Debug|x86.ActiveCfg =
Debug|x64
+ {94D2CD59-A5F3-4504-BF01-0A3B95CE12B5}.Release|Any
CPU.ActiveCfg = Release|x64
{94D2CD59-A5F3-4504-BF01-0A3B95CE12B5}.Release|x64.ActiveCfg =
Release|x64
{94D2CD59-A5F3-4504-BF01-0A3B95CE12B5}.Release|x64.Build.0 =
Release|x64
+ {94D2CD59-A5F3-4504-BF01-0A3B95CE12B5}.Release|x86.ActiveCfg =
Release|x64
+ {4E830BC8-D1CA-40AF-9C9C-D15E193C6585}.Debug|Any CPU.ActiveCfg
= Debug|Any CPU
+ {4E830BC8-D1CA-40AF-9C9C-D15E193C6585}.Debug|Any CPU.Build.0 =
Debug|Any CPU
+ {4E830BC8-D1CA-40AF-9C9C-D15E193C6585}.Debug|x64.ActiveCfg =
Debug|x64
+ {4E830BC8-D1CA-40AF-9C9C-D15E193C6585}.Debug|x64.Build.0 =
Debug|x64
+ {4E830BC8-D1CA-40AF-9C9C-D15E193C6585}.Debug|x86.ActiveCfg =
Debug|x86
+ {4E830BC8-D1CA-40AF-9C9C-D15E193C6585}.Debug|x86.Build.0 =
Debug|x86
+ {4E830BC8-D1CA-40AF-9C9C-D15E193C6585}.Release|Any
CPU.ActiveCfg = Release|Any CPU
+
[jira] [Commented] (GEODE-9464) Add a non-Steeltoe Asp.Net Core SessionState sample app to SessionStateCore
[
https://issues.apache.org/jira/browse/GEODE-9464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404696#comment-17404696
]
ASF GitHub Bot commented on GEODE-9464:
---
mmartell commented on a change in pull request #856:
URL: https://github.com/apache/geode-native/pull/856#discussion_r696083927
##
File path: netcore/AspNetCore GeodeSession
Sample/Extensions/SessionExtensions.cs
##
@@ -0,0 +1,60 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+using System.Text.Json;
+using Microsoft.AspNetCore.Http;
+
+namespace Web.Extensions
+{
+#region snippet1
+public static class SessionExtensions
+{
+public static void Set(this ISession session, string key, T value)
+{
+session.SetString(key, JsonSerializer.Serialize(value));
+}
+
+public static T Get(this ISession session, string key)
+{
+var value = session.GetString(key);
+return value == null ? default :
JsonSerializer.Deserialize(value);
+}
+}
+#endregion
+}
+
+namespace Web.Extensions2
+{
+// Alternate approach
+
+public static class SessionExtensions
+{
+public static void Set(this ISession session, string key, T value)
+{
+session.SetString(key, JsonSerializer.Serialize(value));
+}
+
+public static bool TryGet(this ISession session, string key, out T
value)
+{
+var state = session.GetString(key);
+value = default;
+if (state == null)
+return false;
+value = JsonSerializer.Deserialize(state);
+return true;
+}
+}
+}
Review comment:
Yup
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscr...@geode.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Add a non-Steeltoe Asp.Net Core SessionState sample app to SessionStateCore
> ---
>
> Key: GEODE-9464
> URL: https://issues.apache.org/jira/browse/GEODE-9464
> Project: Geode
> Issue Type: Test
> Components: native client
>Reporter: Michael Martell
>Priority: Major
> Labels: pull-request-available
>
> The current Asp.Net sample app uses Steeltoe for discovery and registration
> of our sessionstate provider. We need a non-Steeltoe sample as well, since
> not everyone uses Steeltoe.
> This will be a good test of our NuGet access to the SessionState Core
> artifacts and its dependencies.
> Note: Ensure that the web application runs on all platforms.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9464) Add a non-Steeltoe Asp.Net Core SessionState sample app to SessionStateCore
[
https://issues.apache.org/jira/browse/GEODE-9464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404695#comment-17404695
]
ASF GitHub Bot commented on GEODE-9464:
---
mmartell commented on a change in pull request #856:
URL: https://github.com/apache/geode-native/pull/856#discussion_r696082552
##
File path: netcore/AspNetCore GeodeSession
Sample/Extensions/SessionExtensions.cs
##
@@ -0,0 +1,60 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+using System.Text.Json;
+using Microsoft.AspNetCore.Http;
+
+namespace Web.Extensions
+{
+#region snippet1
Review comment:
Done.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscr...@geode.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Add a non-Steeltoe Asp.Net Core SessionState sample app to SessionStateCore
> ---
>
> Key: GEODE-9464
> URL: https://issues.apache.org/jira/browse/GEODE-9464
> Project: Geode
> Issue Type: Test
> Components: native client
>Reporter: Michael Martell
>Priority: Major
> Labels: pull-request-available
>
> The current Asp.Net sample app uses Steeltoe for discovery and registration
> of our sessionstate provider. We need a non-Steeltoe sample as well, since
> not everyone uses Steeltoe.
> This will be a good test of our NuGet access to the SessionState Core
> artifacts and its dependencies.
> Note: Ensure that the web application runs on all platforms.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9464) Add a non-Steeltoe Asp.Net Core SessionState sample app to SessionStateCore
[ https://issues.apache.org/jira/browse/GEODE-9464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404694#comment-17404694 ] ASF GitHub Bot commented on GEODE-9464: --- mmartell commented on a change in pull request #856: URL: https://github.com/apache/geode-native/pull/856#discussion_r696080532 ## File path: netcore/AspNetCore GeodeSession Sample/Pages/Shared/_Layout.cshtml ## @@ -0,0 +1,14 @@ + Review comment: Good catch. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@geode.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Add a non-Steeltoe Asp.Net Core SessionState sample app to SessionStateCore > --- > > Key: GEODE-9464 > URL: https://issues.apache.org/jira/browse/GEODE-9464 > Project: Geode > Issue Type: Test > Components: native client >Reporter: Michael Martell >Priority: Major > Labels: pull-request-available > > The current Asp.Net sample app uses Steeltoe for discovery and registration > of our sessionstate provider. We need a non-Steeltoe sample as well, since > not everyone uses Steeltoe. > This will be a good test of our NuGet access to the SessionState Core > artifacts and its dependencies. > Note: Ensure that the web application runs on all platforms. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9435) Implement ZREMRANGEBYRANK Command
[ https://issues.apache.org/jira/browse/GEODE-9435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404683#comment-17404683 ] Ray Ingles commented on GEODE-9435: --- https://github.com/apache/geode/pull/6803 > Implement ZREMRANGEBYRANK Command > - > > Key: GEODE-9435 > URL: https://issues.apache.org/jira/browse/GEODE-9435 > Project: Geode > Issue Type: New Feature > Components: redis >Reporter: Wayne >Assignee: Ray Ingles >Priority: Major > Labels: redis > > Implement the [ZREMRANGEBYRANK|https://redis.io/commands/zremrangebyrank] > command. > > +Acceptance Criteria+ > > The command has been implemented along with appropriate unit tests. > > The command has been added to the AbstractHitsMissesIntegrationTest. The > command has been tested using the redis-cli tool and verified against native > redis. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9535) CI Failure: Tomcat7ClientServerTest > newContainersShouldShareDataAccess
[
https://issues.apache.org/jira/browse/GEODE-9535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ray Ingles updated GEODE-9535:
--
Labels: (was: pull-request-available)
> CI Failure: Tomcat7ClientServerTest > newContainersShouldShareDataAccess
>
>
> Key: GEODE-9535
> URL: https://issues.apache.org/jira/browse/GEODE-9535
> Project: Geode
> Issue Type: Test
> Components: http session
>Reporter: Jens Deppe
>Priority: Major
>
> {noformat}
> > Task :geode-assembly:distributedTest
> org.apache.geode.session.tests.Tomcat7ClientServerTest >
> newContainersShouldShareDataAccess FAILED
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in 'dunit_suspect-vm0.log' at line 423
> [fatal 2021/08/21 21:05:18.691 UTC tid=855]
> Exception in processing request from 10.0.0.108
> java.lang.Exception: Improperly configured client detected - use
> addPoolLocator to configure its locators instead of addPoolServer.
> at
> org.apache.geode.distributed.internal.ProtocolCheckerImpl.checkProtocol(ProtocolCheckerImpl.java:31)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:342)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> ---
> Found suspect string in 'dunit_suspect-vm0.log' at line 540
> [fatal 2021/08/21 21:05:30.875 UTC tid=855]
> Exception in processing request from 10.0.0.108
> java.lang.Exception: Improperly configured client detected - use
> addPoolLocator to configure its locators instead of addPoolServer.
> at
> org.apache.geode.distributed.internal.ProtocolCheckerImpl.checkProtocol(ProtocolCheckerImpl.java:31)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:342)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> at org.junit.Assert.fail(Assert.java:89)
> at
> org.apache.geode.test.dunit.internal.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:409)
> at
> org.apache.geode.test.dunit.internal.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:425)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.after(ClusterStartupRule.java:186)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.access$100(ClusterStartupRule.java:70)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule$1.evaluate(ClusterStartupRule.java:141)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:61)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at
> org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
> at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
> at
> org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:62)
> at
>
[jira] [Assigned] (GEODE-9435) Implement ZREMRANGEBYRANK Command
[ https://issues.apache.org/jira/browse/GEODE-9435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ray Ingles reassigned GEODE-9435: - Assignee: Ray Ingles > Implement ZREMRANGEBYRANK Command > - > > Key: GEODE-9435 > URL: https://issues.apache.org/jira/browse/GEODE-9435 > Project: Geode > Issue Type: New Feature > Components: redis >Reporter: Wayne >Assignee: Ray Ingles >Priority: Major > Labels: redis > > Implement the [ZREMRANGEBYRANK|https://redis.io/commands/zremrangebyrank] > command. > > +Acceptance Criteria+ > > The command has been implemented along with appropriate unit tests. > > The command has been added to the AbstractHitsMissesIntegrationTest. The > command has been tested using the redis-cli tool and verified against native > redis. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9464) Add a non-Steeltoe Asp.Net Core SessionState sample app to SessionStateCore
[
https://issues.apache.org/jira/browse/GEODE-9464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404664#comment-17404664
]
ASF GitHub Bot commented on GEODE-9464:
---
pivotal-jbarrett commented on a change in pull request #856:
URL: https://github.com/apache/geode-native/pull/856#discussion_r696022449
##
File path: netcore/AspNetCore GeodeSession
Sample/Extensions/SessionExtensions.cs
##
@@ -0,0 +1,60 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+using System.Text.Json;
+using Microsoft.AspNetCore.Http;
+
+namespace Web.Extensions
+{
+#region snippet1
Review comment:
I believe or formatting is 2 spaces.
##
File path: netcore/AspNetCore GeodeSession
Sample/Extensions/SessionExtensions.cs
##
@@ -0,0 +1,60 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+using System.Text.Json;
+using Microsoft.AspNetCore.Http;
+
+namespace Web.Extensions
+{
+#region snippet1
+public static class SessionExtensions
+{
+public static void Set(this ISession session, string key, T value)
+{
+session.SetString(key, JsonSerializer.Serialize(value));
+}
+
+public static T Get(this ISession session, string key)
+{
+var value = session.GetString(key);
+return value == null ? default :
JsonSerializer.Deserialize(value);
+}
+}
+#endregion
+}
+
+namespace Web.Extensions2
+{
+// Alternate approach
+
+public static class SessionExtensions
+{
+public static void Set(this ISession session, string key, T value)
+{
+session.SetString(key, JsonSerializer.Serialize(value));
+}
+
+public static bool TryGet(this ISession session, string key, out T
value)
+{
+var state = session.GetString(key);
+value = default;
+if (state == null)
+return false;
+value = JsonSerializer.Deserialize(state);
+return true;
+}
+}
+}
Review comment:
Missing new line.
##
File path: netcore/AspNetCore GeodeSession Sample/Pages/Shared/_Layout.cshtml
##
@@ -0,0 +1,14 @@
+
Review comment:
Will need a license.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscr...@geode.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Add a non-Steeltoe Asp.Net Core SessionState sample app to SessionStateCore
> ---
>
> Key: GEODE-9464
> URL: https://issues.apache.org/jira/browse/GEODE-9464
> Project: Geode
> Issue Type: Test
> Components: native client
>Reporter: Michael Martell
>Priority: Major
> Labels: pull-request-available
>
> The current Asp.Net sample app uses Steeltoe for discovery and registration
> of our sessionstate provider. We need a non-Steeltoe sample as well, since
> not everyone uses Steeltoe.
> This will be a good test of our NuGet access to the SessionState Core
> artifacts and its dependencies.
> Note: Ensure that the web application runs on
[jira] [Created] (GEODE-9550) Native Client user guide: warn against floating point values in keys
Dave Barnes created GEODE-9550: -- Summary: Native Client user guide: warn against floating point values in keys Key: GEODE-9550 URL: https://issues.apache.org/jira/browse/GEODE-9550 Project: Geode Issue Type: Improvement Components: docs, native client Affects Versions: 1.13.4 Reporter: Dave Barnes Request from a community member: You should NEVER use a floating point value as a key, or key component, but for some reason we allow it. Since this can't be prevented in code, warn against this practice in the docs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-9549) Enable .net core tests in CI
Blake Bender created GEODE-9549: --- Summary: Enable .net core tests in CI Key: GEODE-9549 URL: https://issues.apache.org/jira/browse/GEODE-9549 Project: Geode Issue Type: Improvement Components: native client Reporter: Blake Bender The .net core build and tests are integrated into the CI, but test running is currently disabled due to a few issues. These need to be cleaned up, and tests enabled in CI. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9535) CI Failure: Tomcat7ClientServerTest > newContainersShouldShareDataAccess
[
https://issues.apache.org/jira/browse/GEODE-9535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-9535:
--
Labels: pull-request-available (was: )
> CI Failure: Tomcat7ClientServerTest > newContainersShouldShareDataAccess
>
>
> Key: GEODE-9535
> URL: https://issues.apache.org/jira/browse/GEODE-9535
> Project: Geode
> Issue Type: Test
> Components: http session
>Reporter: Jens Deppe
>Priority: Major
> Labels: pull-request-available
>
> {noformat}
> > Task :geode-assembly:distributedTest
> org.apache.geode.session.tests.Tomcat7ClientServerTest >
> newContainersShouldShareDataAccess FAILED
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in 'dunit_suspect-vm0.log' at line 423
> [fatal 2021/08/21 21:05:18.691 UTC tid=855]
> Exception in processing request from 10.0.0.108
> java.lang.Exception: Improperly configured client detected - use
> addPoolLocator to configure its locators instead of addPoolServer.
> at
> org.apache.geode.distributed.internal.ProtocolCheckerImpl.checkProtocol(ProtocolCheckerImpl.java:31)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:342)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> ---
> Found suspect string in 'dunit_suspect-vm0.log' at line 540
> [fatal 2021/08/21 21:05:30.875 UTC tid=855]
> Exception in processing request from 10.0.0.108
> java.lang.Exception: Improperly configured client detected - use
> addPoolLocator to configure its locators instead of addPoolServer.
> at
> org.apache.geode.distributed.internal.ProtocolCheckerImpl.checkProtocol(ProtocolCheckerImpl.java:31)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:342)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> at org.junit.Assert.fail(Assert.java:89)
> at
> org.apache.geode.test.dunit.internal.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:409)
> at
> org.apache.geode.test.dunit.internal.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:425)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.after(ClusterStartupRule.java:186)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.access$100(ClusterStartupRule.java:70)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule$1.evaluate(ClusterStartupRule.java:141)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:61)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at
> org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
> at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
> at
> org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:62)
> at
>
[jira] [Closed] (GEODE-9412) App crashes when translating string with certain Unicode characters (exception thrown across managed/native boundary)
[ https://issues.apache.org/jira/browse/GEODE-9412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Bender closed GEODE-9412. --- > App crashes when translating string with certain Unicode characters > (exception thrown across managed/native boundary) > - > > Key: GEODE-9412 > URL: https://issues.apache.org/jira/browse/GEODE-9412 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Blake Bender >Priority: Major > Labels: pull-request-available > > tl;dr, we're not translating unicode correctly between .net and C++. > When a unicode string comes into the CLI layer, we use > `marshal_as` to translate, then assume this yields UTF-8. In > fact, what it yields is a string encoded in a) whatever the local code page > is for the system, or b) the default code page for the app, if one exists in > the manifest. In the C++ layer, we then assume the string is UTF-8, and for > a PUT, attempt to translate into Java-modified UTF-8, which ends up throwing > an uncaught exception when it encounters a character that is not a valid > UTF-8 start code. When this exception hits the native/managed boundary, the > app crashes. > To avoid this issue, we need to `marshal_as`, then use `std` > conversion functions to arrive at UTF-8, and pass that down to the C++ layer. > We also need to use the reverse process when sending strings back up to CLI. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9412) App crashes when translating string with certain Unicode characters (exception thrown across managed/native boundary)
[ https://issues.apache.org/jira/browse/GEODE-9412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Bender resolved GEODE-9412. - Resolution: Fixed > App crashes when translating string with certain Unicode characters > (exception thrown across managed/native boundary) > - > > Key: GEODE-9412 > URL: https://issues.apache.org/jira/browse/GEODE-9412 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Blake Bender >Priority: Major > Labels: pull-request-available > > tl;dr, we're not translating unicode correctly between .net and C++. > When a unicode string comes into the CLI layer, we use > `marshal_as` to translate, then assume this yields UTF-8. In > fact, what it yields is a string encoded in a) whatever the local code page > is for the system, or b) the default code page for the app, if one exists in > the manifest. In the C++ layer, we then assume the string is UTF-8, and for > a PUT, attempt to translate into Java-modified UTF-8, which ends up throwing > an uncaught exception when it encounters a character that is not a valid > UTF-8 start code. When this exception hits the native/managed boundary, the > app crashes. > To avoid this issue, we need to `marshal_as`, then use `std` > conversion functions to arrive at UTF-8, and pass that down to the C++ layer. > We also need to use the reverse process when sending strings back up to CLI. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9464) Add a non-Steeltoe Asp.Net Core SessionState sample app to SessionStateCore
[
https://issues.apache.org/jira/browse/GEODE-9464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404630#comment-17404630
]
ASF GitHub Bot commented on GEODE-9464:
---
echobravopapa commented on a change in pull request #856:
URL: https://github.com/apache/geode-native/pull/856#discussion_r695969071
##
File path: netcore/geode-dotnet-core.sln
##
@@ -13,35 +13,70 @@ Project("{9A19103F-16F7-4668-BE54-9A1E7A4F7556}") =
"NetCore.Session", "NetCore.
EndProject
Project("{9A19103F-16F7-4668-BE54-9A1E7A4F7556}") =
"NetCore.Session.IntegrationTests",
"NetCore.Session.IntegrationTests\NetCore.Session.IntegrationTests.csproj",
"{94D2CD59-A5F3-4504-BF01-0A3B95CE12B5}"
EndProject
+Project("{9A19103F-16F7-4668-BE54-9A1E7A4F7556}") = "AspNetCore GeodeSession
Sample", "AspNetCore GeodeSession Sample\AspNetCore GeodeSession
Sample.csproj", "{4E830BC8-D1CA-40AF-9C9C-D15E193C6585}"
+EndProject
Global
GlobalSection(SolutionConfigurationPlatforms) = preSolution
+ Debug|Any CPU = Debug|Any CPU
Debug|x64 = Debug|x64
+ Debug|x86 = Debug|x86
+ Release|Any CPU = Release|Any CPU
Release|x64 = Release|x64
+ Release|x86 = Release|x86
EndGlobalSection
GlobalSection(ProjectConfigurationPlatforms) = postSolution
+ {09ABBCE7-B217-43F1-A51B-CC5BDCD8EE98}.Debug|Any CPU.ActiveCfg
= Debug|x64
{09ABBCE7-B217-43F1-A51B-CC5BDCD8EE98}.Debug|x64.ActiveCfg =
Debug|x64
{09ABBCE7-B217-43F1-A51B-CC5BDCD8EE98}.Debug|x64.Build.0 =
Debug|x64
+ {09ABBCE7-B217-43F1-A51B-CC5BDCD8EE98}.Debug|x86.ActiveCfg =
Debug|x64
+ {09ABBCE7-B217-43F1-A51B-CC5BDCD8EE98}.Release|Any
CPU.ActiveCfg = Release|x64
{09ABBCE7-B217-43F1-A51B-CC5BDCD8EE98}.Release|x64.ActiveCfg =
Release|x64
{09ABBCE7-B217-43F1-A51B-CC5BDCD8EE98}.Release|x64.Build.0 =
Release|x64
+ {09ABBCE7-B217-43F1-A51B-CC5BDCD8EE98}.Release|x86.ActiveCfg =
Release|x64
+ {501DEA7E-8985-42A8-8BC9-C073E1B6DFE0}.Debug|Any CPU.ActiveCfg
= Debug|x64
{501DEA7E-8985-42A8-8BC9-C073E1B6DFE0}.Debug|x64.ActiveCfg =
Debug|x64
{501DEA7E-8985-42A8-8BC9-C073E1B6DFE0}.Debug|x64.Build.0 =
Debug|x64
+ {501DEA7E-8985-42A8-8BC9-C073E1B6DFE0}.Debug|x86.ActiveCfg =
Debug|x64
+ {501DEA7E-8985-42A8-8BC9-C073E1B6DFE0}.Release|Any
CPU.ActiveCfg = Release|x64
{501DEA7E-8985-42A8-8BC9-C073E1B6DFE0}.Release|x64.ActiveCfg =
Release|x64
{501DEA7E-8985-42A8-8BC9-C073E1B6DFE0}.Release|x64.Build.0 =
Release|x64
+ {501DEA7E-8985-42A8-8BC9-C073E1B6DFE0}.Release|x86.ActiveCfg =
Release|x64
+ {B88C58EB-B144-403B-85F7-7A5B45E643E3}.Debug|Any CPU.ActiveCfg
= Debug|x64
{B88C58EB-B144-403B-85F7-7A5B45E643E3}.Debug|x64.ActiveCfg =
Debug|x64
{B88C58EB-B144-403B-85F7-7A5B45E643E3}.Debug|x64.Build.0 =
Debug|x64
+ {B88C58EB-B144-403B-85F7-7A5B45E643E3}.Debug|x86.ActiveCfg =
Debug|x64
+ {B88C58EB-B144-403B-85F7-7A5B45E643E3}.Release|Any
CPU.ActiveCfg = Release|x64
{B88C58EB-B144-403B-85F7-7A5B45E643E3}.Release|x64.ActiveCfg =
Release|x64
{B88C58EB-B144-403B-85F7-7A5B45E643E3}.Release|x64.Build.0 =
Release|x64
+ {B88C58EB-B144-403B-85F7-7A5B45E643E3}.Release|x86.ActiveCfg =
Release|x64
+ {94D2CD59-A5F3-4504-BF01-0A3B95CE12B5}.Debug|Any CPU.ActiveCfg
= Debug|x64
{94D2CD59-A5F3-4504-BF01-0A3B95CE12B5}.Debug|x64.ActiveCfg =
Debug|x64
{94D2CD59-A5F3-4504-BF01-0A3B95CE12B5}.Debug|x64.Build.0 =
Debug|x64
+ {94D2CD59-A5F3-4504-BF01-0A3B95CE12B5}.Debug|x86.ActiveCfg =
Debug|x64
+ {94D2CD59-A5F3-4504-BF01-0A3B95CE12B5}.Release|Any
CPU.ActiveCfg = Release|x64
{94D2CD59-A5F3-4504-BF01-0A3B95CE12B5}.Release|x64.ActiveCfg =
Release|x64
{94D2CD59-A5F3-4504-BF01-0A3B95CE12B5}.Release|x64.Build.0 =
Release|x64
+ {94D2CD59-A5F3-4504-BF01-0A3B95CE12B5}.Release|x86.ActiveCfg =
Release|x64
+ {4E830BC8-D1CA-40AF-9C9C-D15E193C6585}.Debug|Any CPU.ActiveCfg
= Debug|Any CPU
+ {4E830BC8-D1CA-40AF-9C9C-D15E193C6585}.Debug|Any CPU.Build.0 =
Debug|Any CPU
+ {4E830BC8-D1CA-40AF-9C9C-D15E193C6585}.Debug|x64.ActiveCfg =
Debug|x64
+ {4E830BC8-D1CA-40AF-9C9C-D15E193C6585}.Debug|x64.Build.0 =
Debug|x64
+ {4E830BC8-D1CA-40AF-9C9C-D15E193C6585}.Debug|x86.ActiveCfg =
Debug|x86
+ {4E830BC8-D1CA-40AF-9C9C-D15E193C6585}.Debug|x86.Build.0 =
Debug|x86
+ {4E830BC8-D1CA-40AF-9C9C-D15E193C6585}.Release|Any
CPU.ActiveCfg = Release|Any CPU
+
[jira] [Updated] (GEODE-9547) Enable Redis Server to Authorize Using Security Manager
[ https://issues.apache.org/jira/browse/GEODE-9547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-9547: - Description: Every Redis Command/API invocation must be authorized against the customer provided Security Manager. The SecurityManager.authorize method must be called for every Redis API call using the principal returned by the SecurityManager.authenticate method during the authentication process. The ResourcePermission passed to the authorize method should be the same for all operations. The actual permission string is TBD - perhaps DATA:WRITE:REDIS_DATA ?? In the future we may provide more fine grained support with different ResourcePermissions for different redis operations. +Acceptance Criteria+ TBD was: Every Redis Command/API invocation must be authorized against the customer provided Security Manager. The SecurityManager.authorize method must be called for every Redis API call using the principal returned by the SecurityManager.authenticate method during the authentication process. The ResourcePermission passed to the authorize method should be the same for all operations. The actual permission string is TBD - perhaps DATA:*:GEODE_FOR_REDIS_DATA ?? In the future we may provide more find grained support with different ResourcePermissions for different redis operations. +Acceptance Criteria+ TBD > Enable Redis Server to Authorize Using Security Manager > --- > > Key: GEODE-9547 > URL: https://issues.apache.org/jira/browse/GEODE-9547 > Project: Geode > Issue Type: New Feature >Reporter: Wayne >Priority: Major > > Every Redis Command/API invocation must be authorized against the customer > provided Security Manager. > > The SecurityManager.authorize method must be called for every Redis API call > using the principal returned by the SecurityManager.authenticate method > during the authentication process. > The ResourcePermission passed to the authorize method should be the same for > all operations. The actual permission string is TBD - perhaps > DATA:WRITE:REDIS_DATA ?? In the future we may provide more fine grained > support with different ResourcePermissions for different redis operations. > +Acceptance Criteria+ > TBD > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9532) CI Failure: DiskDistributedNoAckAsyncRegionDUnitTest > testNoDataSerializer fails with NotSerializableException
[
https://issues.apache.org/jira/browse/GEODE-9532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404599#comment-17404599
]
Jianxia Chen commented on GEODE-9532:
-
https://github.com/apache/geode/pull/6799
> CI Failure: DiskDistributedNoAckAsyncRegionDUnitTest > testNoDataSerializer
> fails with NotSerializableException
> ---
>
> Key: GEODE-9532
> URL: https://issues.apache.org/jira/browse/GEODE-9532
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Donal Evans
>Assignee: Jianxia Chen
>Priority: Major
> Labels: GeodeOperationAPI
>
> {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
>
[jira] [Updated] (GEODE-9464) Add a non-Steeltoe Asp.Net Core SessionState sample app to SessionStateCore
[ https://issues.apache.org/jira/browse/GEODE-9464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-9464: -- Labels: pull-request-available (was: ) > Add a non-Steeltoe Asp.Net Core SessionState sample app to SessionStateCore > --- > > Key: GEODE-9464 > URL: https://issues.apache.org/jira/browse/GEODE-9464 > Project: Geode > Issue Type: Test > Components: native client >Reporter: Michael Martell >Priority: Major > Labels: pull-request-available > > The current Asp.Net sample app uses Steeltoe for discovery and registration > of our sessionstate provider. We need a non-Steeltoe sample as well, since > not everyone uses Steeltoe. > This will be a good test of our NuGet access to the SessionState Core > artifacts and its dependencies. > Note: Ensure that the web application runs on all platforms. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9464) Add a non-Steeltoe Asp.Net Core SessionState sample app to SessionStateCore
[ https://issues.apache.org/jira/browse/GEODE-9464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404590#comment-17404590 ] ASF GitHub Bot commented on GEODE-9464: --- mmartell opened a new pull request #856: URL: https://github.com/apache/geode-native/pull/856 This adds a sample web application illustrating how to use the new GeodeSessionState provider for Asp.Net Core. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@geode.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Add a non-Steeltoe Asp.Net Core SessionState sample app to SessionStateCore > --- > > Key: GEODE-9464 > URL: https://issues.apache.org/jira/browse/GEODE-9464 > Project: Geode > Issue Type: Test > Components: native client >Reporter: Michael Martell >Priority: Major > > The current Asp.Net sample app uses Steeltoe for discovery and registration > of our sessionstate provider. We need a non-Steeltoe sample as well, since > not everyone uses Steeltoe. > This will be a good test of our NuGet access to the SessionState Core > artifacts and its dependencies. > Note: Ensure that the web application runs on all platforms. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9546) Enable Redis Server to Authenticate Using SecurityManager
[ https://issues.apache.org/jira/browse/GEODE-9546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wayne updated GEODE-9546: - Description: The Redis [AUTH|https://redis.io/commands/auth] command must be integrated with the Geode SecurityManager. # Remove the Geode property compatible-with-redis-password that currently being used for the Redis password. # Add a new geode property for the Redis default user ID, compatible-with-redis-username # When a user issues an AUTH Command, the server must call the authenticate method on the customer's SecurityManager with the user (security-username property) and the user provided password (security-password property) and properly handle the AuthenticationFailedException. If the AUTH command was called without a user the value of compatible-with-redis-user should be used** # The Object/Principal returned from a successful authenticate method call must be cached, associated with the client connection, and available for reuse in subsequent authorization calls. **When the AUTH command has a single argument (e.g. AUTH xx) the single argument is interpreted as a password/token and the default Redis user is used for authentication. When the AUTH command has two arguments (e.g. AUTH xx yy) the first argument is interpreted as a username and is used instead of the default Redis user. The second argument is interpreted as a password. +Acceptance Criteria+ When a SecurityManager is configured, Redis clients that don't AUTH with a valid password cannot perform operations. Redis clients that do AUTH with a valid password can perform Redis operations. Until we support ACLS. Use of the AUTH command with more than two arguments is invalid syntax. was: The Redis [AUTH|https://redis.io/commands/auth] command must be integrated with the Geode SecurityManager. # Remove the Geode property compatible-with-redis-password that currently being used for the Redis password. # Add a new geode property for the Redis default user ID, compatible-with-redis-username # When a user issues an AUTH Command, the server must call the authenticate method on the customer's SecurityManager with the user (security-username property) and the user provided password (security-password property) and properly handle the AuthenticationFailedException. If the AUTH command was called without a user the value of compatible-with-redis-user should be used. # The Object/Principal returned from a successful authenticate method call must be cached, associated with the client connection, and available for reuse in subsequent authorization calls. +Acceptance Criteria+ When a security manager is configured, redis clients that don't AUTH with a valid password cannot perform operations. Redis clients that do AUTH with a valid password can perform redis operations. > Enable Redis Server to Authenticate Using SecurityManager > - > > Key: GEODE-9546 > URL: https://issues.apache.org/jira/browse/GEODE-9546 > Project: Geode > Issue Type: New Feature >Reporter: Wayne >Priority: Major > > The Redis [AUTH|https://redis.io/commands/auth] command must be integrated > with the Geode SecurityManager. > # Remove the Geode property compatible-with-redis-password that currently > being used for the Redis password. > # Add a new geode property for the Redis default user ID, > compatible-with-redis-username > # When a user issues an AUTH Command, the server must call the authenticate > method on the customer's SecurityManager with the user (security-username > property) and the user provided password (security-password property) and > properly handle the AuthenticationFailedException. If the AUTH command was > called without a user the value of compatible-with-redis-user should be used** > # The Object/Principal returned from a successful authenticate method call > must be cached, associated with the client connection, and available for > reuse in subsequent authorization calls. > **When the AUTH command has a single argument (e.g. AUTH xx) the single > argument is interpreted as a password/token and the default Redis user is > used for authentication. When the AUTH command has two arguments (e.g. AUTH > xx yy) the first argument is interpreted as a username and is used > instead of the default Redis user. The second argument is interpreted as a > password. > +Acceptance Criteria+ > > When a SecurityManager is configured, Redis clients that don't AUTH with a > valid password cannot perform operations. Redis clients that do AUTH with a > valid password can perform Redis operations. Until we support ACLS. Use of > the AUTH command with more than two arguments is invalid syntax. > > -- This message was sent by Atlassian Jira
[jira] [Updated] (GEODE-9546) Enable Redis Server to Authenticate Using SecurityManager
[ https://issues.apache.org/jira/browse/GEODE-9546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-9546: - Description: The Redis [AUTH|https://redis.io/commands/auth] command must be integrated with the Geode SecurityManager. # Remove the Geode property compatible-with-redis-password that currently being used for the Redis password. # Add a new geode property for the Redis default user ID, compatible-with-redis-username # When a user issues an AUTH Command, the server must call the authenticate method on the customer's SecurityManager with the user (security-username property) and the user provided password (security-password property) and properly handle the AuthenticationFailedException. If the AUTH command was called without a user the value of compatible-with-redis-user should be used. # The Object/Principal returned from a successful authenticate method call must be cached, associated with the client connection, and available for reuse in subsequent authorization calls. +Acceptance Criteria+ When a security manager is configured, redis clients that don't AUTH with a valid password cannot perform operations. Redis clients that do AUTH with a valid password can perform redis operations. was: The Redis [AUTH|https://redis.io/commands/auth] command must be integrated with the Geode SecurityManager. # Remove the Geode property _compatible-with-redis-password_, that is currently being used for the Redis password. # Add a new geode property for the Redis default user ID, _compatible-with-redis-user_ # When a user issues an AUTH Command, the server must call the authenticate method on the customer's SecurityManager with the Redis user (security-username property) and the user provided password (security-password property) and properly handle the AuthenticationFailedException.** # The Object/Principal returned from a successful authenticate method call must be cached, associated with the client connection, and available for reuse in subsequent authorization calls. ** When the AUTH command is provided with a single argument, e.g. _AUTH xx_, the +xx+ is interpreted as a password and the default Redis user is used for authentication. When the command is provided with two arguments, e.g. AUTH xx yy, xx is interpreted as a user name and yy is interpreted as the password. +Acceptance Criteria+ When a security manager is configured, Redis clients that don't AUTH with a valid password cannot perform operations. Redis clients that do AUTH with a valid password can perform Redis operations. Until we support ACLs, issuing the AUTH command with more than two arguments is invalid. Appropriate tests written to ensure correct behavior and avoid regressions. > Enable Redis Server to Authenticate Using SecurityManager > - > > Key: GEODE-9546 > URL: https://issues.apache.org/jira/browse/GEODE-9546 > Project: Geode > Issue Type: New Feature >Reporter: Wayne >Priority: Major > > The Redis [AUTH|https://redis.io/commands/auth] command must be integrated > with the Geode SecurityManager. > # Remove the Geode property compatible-with-redis-password that currently > being used for the Redis password. > # Add a new geode property for the Redis default user ID, > compatible-with-redis-username > # When a user issues an AUTH Command, the server must call the authenticate > method on the customer's SecurityManager with the user (security-username > property) and the user provided password (security-password property) and > properly handle the AuthenticationFailedException. If the AUTH command was > called without a user the value of compatible-with-redis-user should be used. > # The Object/Principal returned from a successful authenticate method call > must be cached, associated with the client connection, and available for > reuse in subsequent authorization calls. > +Acceptance Criteria+ > > When a security manager is configured, redis clients that don't AUTH with a > valid password cannot perform operations. Redis clients that do AUTH with a > valid password can perform redis operations. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9546) Enable Redis Server to Authenticate Using SecurityManager
[ https://issues.apache.org/jira/browse/GEODE-9546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wayne updated GEODE-9546: - Description: The Redis [AUTH|https://redis.io/commands/auth] command must be integrated with the Geode SecurityManager. # Remove the Geode property _compatible-with-redis-password_, that is currently being used for the Redis password. # Add a new geode property for the Redis default user ID, _compatible-with-redis-user_ # When a user issues an AUTH Command, the server must call the authenticate method on the customer's SecurityManager with the Redis user (security-username property) and the user provided password (security-password property) and properly handle the AuthenticationFailedException.** # The Object/Principal returned from a successful authenticate method call must be cached, associated with the client connection, and available for reuse in subsequent authorization calls. ** When the AUTH command is provided with a single argument, e.g. _AUTH xx_, the +xx+ is interpreted as a password and the default Redis user is used for authentication. When the command is provided with two arguments, e.g. AUTH xx yy, xx is interpreted as a user name and yy is interpreted as the password. +Acceptance Criteria+ When a security manager is configured, Redis clients that don't AUTH with a valid password cannot perform operations. Redis clients that do AUTH with a valid password can perform Redis operations. Until we support ACLs, issuing the AUTH command with more than two arguments is invalid. Appropriate tests written to ensure correct behavior and avoid regressions. was: The Redis [AUTH|https://redis.io/commands/auth] command must be integrated with the Geode SecurityManager. # Remove the Geode property compatible-with-redis-password that currently being used for the Redis password. # Add a new geode property for the Redis default user ID, compatible-with-redis-user # When a user issues an AUTH Command, the server must call the authenticate method on the customer's SecurityManager with the user (security-username property) and the user provided password (security-password property) and properly handle the AuthenticationFailedException. If the AUTH command was called without a user the value of compatible-with-redis-user should be used. # The Object/Principal returned from a successful authenticate method call must be cached, associated with the client connection, and available for reuse in subsequent authorization calls. +Acceptance Criteria+ When a security manager is configured, redis clients that don't AUTH with a valid password cannot perform operations. Redis clients that do AUTH with a valid password can perform redis operations. > Enable Redis Server to Authenticate Using SecurityManager > - > > Key: GEODE-9546 > URL: https://issues.apache.org/jira/browse/GEODE-9546 > Project: Geode > Issue Type: New Feature >Reporter: Wayne >Priority: Major > > The Redis [AUTH|https://redis.io/commands/auth] command must be integrated > with the Geode SecurityManager. > # Remove the Geode property _compatible-with-redis-password_, that is > currently being used for the Redis password. > # Add a new geode property for the Redis default user ID, > _compatible-with-redis-user_ > # When a user issues an AUTH Command, the server must call the authenticate > method on the customer's SecurityManager with the Redis user > (security-username property) and the user provided password > (security-password property) and properly handle the > AuthenticationFailedException.** > # The Object/Principal returned from a successful authenticate method call > must be cached, associated with the client connection, and available for > reuse in subsequent authorization calls. > ** When the AUTH command is provided with a single argument, e.g. _AUTH > xx_, the +xx+ is interpreted as a password and the default Redis user > is used for authentication. When the command is provided with two arguments, > e.g. AUTH xx yy, xx is interpreted as a user name and yy is > interpreted as the password. > +Acceptance Criteria+ > When a security manager is configured, Redis clients that don't AUTH with a > valid password cannot perform operations. Redis clients that do AUTH with a > valid password can perform Redis operations. Until we support ACLs, issuing > the AUTH command with more than two arguments is invalid. > Appropriate tests written to ensure correct behavior and avoid regressions. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9546) Enable Redis Server to Authenticate Using SecurityManager
[ https://issues.apache.org/jira/browse/GEODE-9546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-9546: - Description: The Redis [AUTH|https://redis.io/commands/auth] command must be integrated with the Geode SecurityManager. # Remove the Geode property compatible-with-redis-password that currently being used for the Redis password. # Add a new geode property for the Redis default user ID, compatible-with-redis-user # When a user issues an AUTH Command, the server must call the authenticate method on the customer's SecurityManager with the user (security-username property) and the user provided password (security-password property) and properly handle the AuthenticationFailedException. If the AUTH command was called without a user the value of compatible-with-redis-user should be used. # The Object/Principal returned from a successful authenticate method call must be cached, associated with the client connection, and available for reuse in subsequent authorization calls. +Acceptance Criteria+ When a security manager is configured, redis clients that don't AUTH with a valid password cannot perform operations. Redis clients that do AUTH with a valid password can perform redis operations. was: The Redis [AUTH|https://redis.io/commands/auth] command must be integrated with the Geode SecurityManager. # Remove the Geode property compatible-with-redis-password that currently being used for the Redis password. # Add a new geode property for the Redis default user ID, compatible-with-redis-user # When a user issues an AUTH Command, the server must call the authenticate method on the customer's SecurityManager with the default Redis User (security-username property) and the user provided password (security-password property) and properly handle the AuthenticationFailedException. # The Object/Principal returned from a successful authenticate method call must be cached, associated with the client connection, and available for reuse in subsequent authorization calls. +Acceptance Criteria+ When a security manager is configured, redis clients that don't AUTH with a valid password cannot perform operations. Redis clients that do AUTH with a valid password can perform redis operations. > Enable Redis Server to Authenticate Using SecurityManager > - > > Key: GEODE-9546 > URL: https://issues.apache.org/jira/browse/GEODE-9546 > Project: Geode > Issue Type: New Feature >Reporter: Wayne >Priority: Major > > The Redis [AUTH|https://redis.io/commands/auth] command must be integrated > with the Geode SecurityManager. > # Remove the Geode property compatible-with-redis-password that currently > being used for the Redis password. > # Add a new geode property for the Redis default user ID, > compatible-with-redis-user > # When a user issues an AUTH Command, the server must call the authenticate > method on the customer's SecurityManager with the user (security-username > property) and the user provided password (security-password property) and > properly handle the AuthenticationFailedException. If the AUTH command was > called without a user the value of compatible-with-redis-user should be used. > # The Object/Principal returned from a successful authenticate method call > must be cached, associated with the client connection, and available for > reuse in subsequent authorization calls. > +Acceptance Criteria+ > > When a security manager is configured, redis clients that don't AUTH with a > valid password cannot perform operations. Redis clients that do AUTH with a > valid password can perform redis operations. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (GEODE-9369) Command to copy region entries from a WAN site to another.
[ https://issues.apache.org/jira/browse/GEODE-9369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kamilla Aslami reopened GEODE-9369: --- Reopening this issue because of the failures in WanCopyRegionFunctionTest on Windows. > Command to copy region entries from a WAN site to another. > -- > > Key: GEODE-9369 > URL: https://issues.apache.org/jira/browse/GEODE-9369 > Project: Geode > Issue Type: New Feature > Components: wan >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > As described in RFC: > [https://cwiki.apache.org/confluence/display/GEODE/Geode+Command+to+replicate+region+data+from+one+site+to+another+connected+via+WAN] > it is proposed to implement a command that copies the entries of a region in > a WAN site to the same region in another WAN site by using WAN replication. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9530) CI Failure: ClassNotFoundException in TomcatSessionBackwardsCompatibilityTomcat7079WithOldModuleCanDoPutsTest
[
https://issues.apache.org/jira/browse/GEODE-9530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-9530:
-
Labels: (was: blocks-1.14.0)
> 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
>Assignee: Benjamin P Ross
>Priority: Major
>
> {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:
>
[jira] [Commented] (GEODE-9532) CI Failure: DiskDistributedNoAckAsyncRegionDUnitTest > testNoDataSerializer fails with NotSerializableException
[
https://issues.apache.org/jira/browse/GEODE-9532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404580#comment-17404580
]
Anthony Baker commented on GEODE-9532:
--
Removed 1.14 blocker label based on above analysis.
> CI Failure: DiskDistributedNoAckAsyncRegionDUnitTest > testNoDataSerializer
> fails with NotSerializableException
> ---
>
> Key: GEODE-9532
> URL: https://issues.apache.org/jira/browse/GEODE-9532
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Donal Evans
>Assignee: Jianxia Chen
>Priority: Major
> Labels: GeodeOperationAPI
>
> {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
>
[jira] [Commented] (GEODE-9530) CI Failure: ClassNotFoundException in TomcatSessionBackwardsCompatibilityTomcat7079WithOldModuleCanDoPutsTest
[
https://issues.apache.org/jira/browse/GEODE-9530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404581#comment-17404581
]
Anthony Baker commented on GEODE-9530:
--
Removed 1.14 blocker label based on above analysis.
> 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
>Assignee: Benjamin P Ross
>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:
>
[jira] [Updated] (GEODE-9532) CI Failure: DiskDistributedNoAckAsyncRegionDUnitTest > testNoDataSerializer fails with NotSerializableException
[
https://issues.apache.org/jira/browse/GEODE-9532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-9532:
-
Labels: GeodeOperationAPI (was: GeodeOperationAPI blocks-1.14.0)
> CI Failure: DiskDistributedNoAckAsyncRegionDUnitTest > testNoDataSerializer
> fails with NotSerializableException
> ---
>
> Key: GEODE-9532
> URL: https://issues.apache.org/jira/browse/GEODE-9532
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Donal Evans
>Assignee: Jianxia Chen
>Priority: Major
> Labels: GeodeOperationAPI
>
> {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
>
[jira] [Issue Comment Deleted] (GEODE-9530) CI Failure: ClassNotFoundException in TomcatSessionBackwardsCompatibilityTomcat7079WithOldModuleCanDoPutsTest
[
https://issues.apache.org/jira/browse/GEODE-9530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Murmann updated GEODE-9530:
-
Comment: was deleted
(was: [~Sarm Kahel] Do you agree with Dan's recommendation?)
> 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
>Assignee: Benjamin P Ross
>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:
>
[jira] [Commented] (GEODE-9530) CI Failure: ClassNotFoundException in TomcatSessionBackwardsCompatibilityTomcat7079WithOldModuleCanDoPutsTest
[
https://issues.apache.org/jira/browse/GEODE-9530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404566#comment-17404566
]
Alexander Murmann commented on GEODE-9530:
--
[~Sarm Kahel] Do you agree with Dan's recommendation?
> 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
>Assignee: Benjamin P Ross
>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:
>
[jira] [Commented] (GEODE-9369) Command to copy region entries from a WAN site to another.
[ https://issues.apache.org/jira/browse/GEODE-9369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404547#comment-17404547 ] Geode Integration commented on GEODE-9369: -- Seen in [windows-unit-test-openjdk8 #143|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/windows-unit-test-openjdk8/builds/143] ... see [test results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0436/test-results/test/1629876775/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0436/test-artifacts/1629876775/windows-unittestfiles-openjdk8-1.15.0-build.0436.tgz]. > Command to copy region entries from a WAN site to another. > -- > > Key: GEODE-9369 > URL: https://issues.apache.org/jira/browse/GEODE-9369 > Project: Geode > Issue Type: New Feature > Components: wan >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > As described in RFC: > [https://cwiki.apache.org/confluence/display/GEODE/Geode+Command+to+replicate+region+data+from+one+site+to+another+connected+via+WAN] > it is proposed to implement a command that copies the entries of a region in > a WAN site to the same region in another WAN site by using WAN replication. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9369) Command to copy region entries from a WAN site to another.
[ https://issues.apache.org/jira/browse/GEODE-9369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404546#comment-17404546 ] Geode Integration commented on GEODE-9369: -- Seen in [windows-unit-test-openjdk11 #143|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/windows-unit-test-openjdk11/builds/143] ... see [test results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0436/test-results/test/1629876885/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0436/test-artifacts/1629876885/windows-unittestfiles-openjdk11-1.15.0-build.0436.tgz]. > Command to copy region entries from a WAN site to another. > -- > > Key: GEODE-9369 > URL: https://issues.apache.org/jira/browse/GEODE-9369 > Project: Geode > Issue Type: New Feature > Components: wan >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > As described in RFC: > [https://cwiki.apache.org/confluence/display/GEODE/Geode+Command+to+replicate+region+data+from+one+site+to+another+connected+via+WAN] > it is proposed to implement a command that copies the entries of a region in > a WAN site to the same region in another WAN site by using WAN replication. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9340) Benchmark instability in PartitionedPutLongBenchmark
[
https://issues.apache.org/jira/browse/GEODE-9340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404529#comment-17404529
]
Geode Integration commented on GEODE-9340:
--
Seen in [benchmark-base
#144|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/benchmark-base/builds/144].
> Benchmark instability in PartitionedPutLongBenchmark
>
>
> Key: GEODE-9340
> URL: https://issues.apache.org/jira/browse/GEODE-9340
> Project: Geode
> Issue Type: Bug
> Components: benchmarks
>Affects Versions: 1.15.0
>Reporter: Sarah Abbey
>Assignee: Hale Bales
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.13.3, 1.13.4, 1.14.0, 1.15.0
>
>
> PartitionedPutLongBenchmark failed in CI
> (https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/benchmark-base/builds/6):
> {code:java}
> This is ITERATION 1 of benchmarking against baseline.
> P2pPartitionedGetBenchmark avg ops/sec
> Baseline:825011.38 Test:835847.67 Difference: +1.3%
> avg latency
> Baseline:871392.31 Test:859444.66 Difference: -1.4%
> P2pPartitionedPutBenchmark avg ops/sec
> Baseline:123838.43 Test:122686.30 Difference: -0.9%
> avg latency
> Baseline: 6015719.73 Test: 6119472.19 Difference: +1.7%
> P2pPartitionedPutBytesBenchmark avg ops/sec
> Baseline:174887.77 Test:171040.93 Difference: -2.2%
> avg latency
> Baseline: 4145337.60 Test: 4236159.60 Difference: +2.2%
> PartitionedFunctionExecutionBenchmark avg ops/sec
> Baseline:248635.36 Test:261498.94 Difference: +5.2%
> avg latency
> Baseline:867122.63 Test:824550.34 Difference: -4.9%
> PartitionedFunctionExecutionWithArgumentsBenchmark avg ops/sec
> Baseline:280071.19 Test:275305.31 Difference: -1.7%
> avg latency
> Baseline: 1026643.12 Test: 1044307.43 Difference: +1.7%
> PartitionedFunctionExecutionWithFiltersBenchmark avg ops/sec
> Baseline:301416.23 Test:304317.30 Difference: +1.0%
> avg latency
> Baseline: 1908390.88 Test: 1890040.46 Difference: -1.0%
> PartitionedGetBenchmark avg ops/sec
> Baseline:790800.52 Test:784514.74 Difference: -0.8%
> avg latency
> Baseline:908357.58 Test:915790.96 Difference: +0.8%
> PartitionedGetLongBenchmark avg ops/sec
> Baseline: 1020821.32 Test:996529.93 Difference: -2.4%
> avg latency
> Baseline:703761.09 Test:720744.36 Difference: +2.4%
> PartitionedGetStringBenchmark avg ops/sec
> Baseline: 1028992.93 Test: 1010447.47 Difference: -1.8%
> avg latency
> Baseline:698009.55 Test:710765.29 Difference: +1.8%
> PartitionedIndexedQueryBenchmark avg ops/sec
> Baseline: 30868.78 Test: 31478.90 Difference: +2.0%
> avg latency
> Baseline: 18670093.21 Test: 18278083.16 Difference: -2.1%
> PartitionedNonIndexedQueryBenchmark avg ops/sec
> Baseline:99.45 Test: 101.97 Difference: +2.5%
> avg latency
> Baseline: 723415530.75 Test: 705653061.86 Difference: -2.5%
> PartitionedPutAllBenchmark avg ops/sec
> Baseline: 7921.61 Test: 7816.66 Difference: -1.3%
> avg latency
> Baseline: 18172638.37 Test: 18416169.28 Difference: +1.3%
> PartitionedPutAllLongBenchmark avg ops/sec
> Baseline: 1379.53 Test: 1169.16 Difference: -15.2%
> avg latency
> Baseline: 105140260.44 Test: 123722914.94 Difference: +17.7%
> PartitionedPutBenchmark avg ops/sec
> Baseline:474986.11 Test:467924.19
[jira] [Commented] (GEODE-9369) Command to copy region entries from a WAN site to another.
[ https://issues.apache.org/jira/browse/GEODE-9369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404221#comment-17404221 ] ASF subversion and git services commented on GEODE-9369: Commit c9d465b1e77dbc7bcc87eaea3522029530bb2b2b in geode's branch refs/heads/develop from Alberto Gomez [ https://gitbox.apache.org/repos/asf?p=geode.git;h=c9d465b ] GEODE-9369: Command to copy region entries from a WAN site to another (#6601) * GEODE-9369: Command to copy region entries from a WAN site to another The command has been implemented as proposed in https://cwiki.apache.org/confluence/display/GEODE/Geode+Command+to+replicate+region+data+from+one+site+to+another+connected+via+WAN with some modifications with respect to the initial proposal. The command will get the entries of a region in a WAN site and will put them in batches that will be sent by a gateway sender to a remote WAN site. * GEODE-9369: Remove comments added to geode-gfsh/src/test/resources/expected-pom.xml * GEODE-9369: Changes after review * GEODE-9369: Update with Kirk's review comments * GEODE-9369: Update with boglesby's review comments * GEODE-9369: Changes after boglesby's review * GEODE-9369: Updated with davebarnes97's review comments. * GEODE-9369: More changes after davebarnes97's review * GEODE-9369: Updated with DonalEvan's comments * GEODE-9369: Small refactoring: Use CompletableFuture instead of Callable + FutureTask * GEODE-9369: Fix race condition added in previous commit * GEODE-9369: Small change of re-review from DonalEvans * GEODE-9369: Fix esporadic test failures due to error log. * GEODE-9369: Changes required after rebasing to develop > Command to copy region entries from a WAN site to another. > -- > > Key: GEODE-9369 > URL: https://issues.apache.org/jira/browse/GEODE-9369 > Project: Geode > Issue Type: New Feature > Components: wan >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > As described in RFC: > [https://cwiki.apache.org/confluence/display/GEODE/Geode+Command+to+replicate+region+data+from+one+site+to+another+connected+via+WAN] > it is proposed to implement a command that copies the entries of a region in > a WAN site to the same region in another WAN site by using WAN replication. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9369) Command to copy region entries from a WAN site to another.
[ https://issues.apache.org/jira/browse/GEODE-9369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404216#comment-17404216 ] ASF subversion and git services commented on GEODE-9369: Commit c9d465b1e77dbc7bcc87eaea3522029530bb2b2b in geode's branch refs/heads/develop from Alberto Gomez [ https://gitbox.apache.org/repos/asf?p=geode.git;h=c9d465b ] GEODE-9369: Command to copy region entries from a WAN site to another (#6601) * GEODE-9369: Command to copy region entries from a WAN site to another The command has been implemented as proposed in https://cwiki.apache.org/confluence/display/GEODE/Geode+Command+to+replicate+region+data+from+one+site+to+another+connected+via+WAN with some modifications with respect to the initial proposal. The command will get the entries of a region in a WAN site and will put them in batches that will be sent by a gateway sender to a remote WAN site. * GEODE-9369: Remove comments added to geode-gfsh/src/test/resources/expected-pom.xml * GEODE-9369: Changes after review * GEODE-9369: Update with Kirk's review comments * GEODE-9369: Update with boglesby's review comments * GEODE-9369: Changes after boglesby's review * GEODE-9369: Updated with davebarnes97's review comments. * GEODE-9369: More changes after davebarnes97's review * GEODE-9369: Updated with DonalEvan's comments * GEODE-9369: Small refactoring: Use CompletableFuture instead of Callable + FutureTask * GEODE-9369: Fix race condition added in previous commit * GEODE-9369: Small change of re-review from DonalEvans * GEODE-9369: Fix esporadic test failures due to error log. * GEODE-9369: Changes required after rebasing to develop > Command to copy region entries from a WAN site to another. > -- > > Key: GEODE-9369 > URL: https://issues.apache.org/jira/browse/GEODE-9369 > Project: Geode > Issue Type: New Feature > Components: wan >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > As described in RFC: > [https://cwiki.apache.org/confluence/display/GEODE/Geode+Command+to+replicate+region+data+from+one+site+to+another+connected+via+WAN] > it is proposed to implement a command that copies the entries of a region in > a WAN site to the same region in another WAN site by using WAN replication. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9369) Command to copy region entries from a WAN site to another.
[ https://issues.apache.org/jira/browse/GEODE-9369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404224#comment-17404224 ] ASF subversion and git services commented on GEODE-9369: Commit c9d465b1e77dbc7bcc87eaea3522029530bb2b2b in geode's branch refs/heads/develop from Alberto Gomez [ https://gitbox.apache.org/repos/asf?p=geode.git;h=c9d465b ] GEODE-9369: Command to copy region entries from a WAN site to another (#6601) * GEODE-9369: Command to copy region entries from a WAN site to another The command has been implemented as proposed in https://cwiki.apache.org/confluence/display/GEODE/Geode+Command+to+replicate+region+data+from+one+site+to+another+connected+via+WAN with some modifications with respect to the initial proposal. The command will get the entries of a region in a WAN site and will put them in batches that will be sent by a gateway sender to a remote WAN site. * GEODE-9369: Remove comments added to geode-gfsh/src/test/resources/expected-pom.xml * GEODE-9369: Changes after review * GEODE-9369: Update with Kirk's review comments * GEODE-9369: Update with boglesby's review comments * GEODE-9369: Changes after boglesby's review * GEODE-9369: Updated with davebarnes97's review comments. * GEODE-9369: More changes after davebarnes97's review * GEODE-9369: Updated with DonalEvan's comments * GEODE-9369: Small refactoring: Use CompletableFuture instead of Callable + FutureTask * GEODE-9369: Fix race condition added in previous commit * GEODE-9369: Small change of re-review from DonalEvans * GEODE-9369: Fix esporadic test failures due to error log. * GEODE-9369: Changes required after rebasing to develop > Command to copy region entries from a WAN site to another. > -- > > Key: GEODE-9369 > URL: https://issues.apache.org/jira/browse/GEODE-9369 > Project: Geode > Issue Type: New Feature > Components: wan >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > As described in RFC: > [https://cwiki.apache.org/confluence/display/GEODE/Geode+Command+to+replicate+region+data+from+one+site+to+another+connected+via+WAN] > it is proposed to implement a command that copies the entries of a region in > a WAN site to the same region in another WAN site by using WAN replication. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9369) Command to copy region entries from a WAN site to another.
[ https://issues.apache.org/jira/browse/GEODE-9369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404218#comment-17404218 ] ASF subversion and git services commented on GEODE-9369: Commit c9d465b1e77dbc7bcc87eaea3522029530bb2b2b in geode's branch refs/heads/develop from Alberto Gomez [ https://gitbox.apache.org/repos/asf?p=geode.git;h=c9d465b ] GEODE-9369: Command to copy region entries from a WAN site to another (#6601) * GEODE-9369: Command to copy region entries from a WAN site to another The command has been implemented as proposed in https://cwiki.apache.org/confluence/display/GEODE/Geode+Command+to+replicate+region+data+from+one+site+to+another+connected+via+WAN with some modifications with respect to the initial proposal. The command will get the entries of a region in a WAN site and will put them in batches that will be sent by a gateway sender to a remote WAN site. * GEODE-9369: Remove comments added to geode-gfsh/src/test/resources/expected-pom.xml * GEODE-9369: Changes after review * GEODE-9369: Update with Kirk's review comments * GEODE-9369: Update with boglesby's review comments * GEODE-9369: Changes after boglesby's review * GEODE-9369: Updated with davebarnes97's review comments. * GEODE-9369: More changes after davebarnes97's review * GEODE-9369: Updated with DonalEvan's comments * GEODE-9369: Small refactoring: Use CompletableFuture instead of Callable + FutureTask * GEODE-9369: Fix race condition added in previous commit * GEODE-9369: Small change of re-review from DonalEvans * GEODE-9369: Fix esporadic test failures due to error log. * GEODE-9369: Changes required after rebasing to develop > Command to copy region entries from a WAN site to another. > -- > > Key: GEODE-9369 > URL: https://issues.apache.org/jira/browse/GEODE-9369 > Project: Geode > Issue Type: New Feature > Components: wan >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > As described in RFC: > [https://cwiki.apache.org/confluence/display/GEODE/Geode+Command+to+replicate+region+data+from+one+site+to+another+connected+via+WAN] > it is proposed to implement a command that copies the entries of a region in > a WAN site to the same region in another WAN site by using WAN replication. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9369) Command to copy region entries from a WAN site to another.
[ https://issues.apache.org/jira/browse/GEODE-9369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404223#comment-17404223 ] ASF subversion and git services commented on GEODE-9369: Commit c9d465b1e77dbc7bcc87eaea3522029530bb2b2b in geode's branch refs/heads/develop from Alberto Gomez [ https://gitbox.apache.org/repos/asf?p=geode.git;h=c9d465b ] GEODE-9369: Command to copy region entries from a WAN site to another (#6601) * GEODE-9369: Command to copy region entries from a WAN site to another The command has been implemented as proposed in https://cwiki.apache.org/confluence/display/GEODE/Geode+Command+to+replicate+region+data+from+one+site+to+another+connected+via+WAN with some modifications with respect to the initial proposal. The command will get the entries of a region in a WAN site and will put them in batches that will be sent by a gateway sender to a remote WAN site. * GEODE-9369: Remove comments added to geode-gfsh/src/test/resources/expected-pom.xml * GEODE-9369: Changes after review * GEODE-9369: Update with Kirk's review comments * GEODE-9369: Update with boglesby's review comments * GEODE-9369: Changes after boglesby's review * GEODE-9369: Updated with davebarnes97's review comments. * GEODE-9369: More changes after davebarnes97's review * GEODE-9369: Updated with DonalEvan's comments * GEODE-9369: Small refactoring: Use CompletableFuture instead of Callable + FutureTask * GEODE-9369: Fix race condition added in previous commit * GEODE-9369: Small change of re-review from DonalEvans * GEODE-9369: Fix esporadic test failures due to error log. * GEODE-9369: Changes required after rebasing to develop > Command to copy region entries from a WAN site to another. > -- > > Key: GEODE-9369 > URL: https://issues.apache.org/jira/browse/GEODE-9369 > Project: Geode > Issue Type: New Feature > Components: wan >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > As described in RFC: > [https://cwiki.apache.org/confluence/display/GEODE/Geode+Command+to+replicate+region+data+from+one+site+to+another+connected+via+WAN] > it is proposed to implement a command that copies the entries of a region in > a WAN site to the same region in another WAN site by using WAN replication. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9369) Command to copy region entries from a WAN site to another.
[ https://issues.apache.org/jira/browse/GEODE-9369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404220#comment-17404220 ] ASF subversion and git services commented on GEODE-9369: Commit c9d465b1e77dbc7bcc87eaea3522029530bb2b2b in geode's branch refs/heads/develop from Alberto Gomez [ https://gitbox.apache.org/repos/asf?p=geode.git;h=c9d465b ] GEODE-9369: Command to copy region entries from a WAN site to another (#6601) * GEODE-9369: Command to copy region entries from a WAN site to another The command has been implemented as proposed in https://cwiki.apache.org/confluence/display/GEODE/Geode+Command+to+replicate+region+data+from+one+site+to+another+connected+via+WAN with some modifications with respect to the initial proposal. The command will get the entries of a region in a WAN site and will put them in batches that will be sent by a gateway sender to a remote WAN site. * GEODE-9369: Remove comments added to geode-gfsh/src/test/resources/expected-pom.xml * GEODE-9369: Changes after review * GEODE-9369: Update with Kirk's review comments * GEODE-9369: Update with boglesby's review comments * GEODE-9369: Changes after boglesby's review * GEODE-9369: Updated with davebarnes97's review comments. * GEODE-9369: More changes after davebarnes97's review * GEODE-9369: Updated with DonalEvan's comments * GEODE-9369: Small refactoring: Use CompletableFuture instead of Callable + FutureTask * GEODE-9369: Fix race condition added in previous commit * GEODE-9369: Small change of re-review from DonalEvans * GEODE-9369: Fix esporadic test failures due to error log. * GEODE-9369: Changes required after rebasing to develop > Command to copy region entries from a WAN site to another. > -- > > Key: GEODE-9369 > URL: https://issues.apache.org/jira/browse/GEODE-9369 > Project: Geode > Issue Type: New Feature > Components: wan >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > As described in RFC: > [https://cwiki.apache.org/confluence/display/GEODE/Geode+Command+to+replicate+region+data+from+one+site+to+another+connected+via+WAN] > it is proposed to implement a command that copies the entries of a region in > a WAN site to the same region in another WAN site by using WAN replication. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9369) Command to copy region entries from a WAN site to another.
[ https://issues.apache.org/jira/browse/GEODE-9369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404215#comment-17404215 ] ASF subversion and git services commented on GEODE-9369: Commit c9d465b1e77dbc7bcc87eaea3522029530bb2b2b in geode's branch refs/heads/develop from Alberto Gomez [ https://gitbox.apache.org/repos/asf?p=geode.git;h=c9d465b ] GEODE-9369: Command to copy region entries from a WAN site to another (#6601) * GEODE-9369: Command to copy region entries from a WAN site to another The command has been implemented as proposed in https://cwiki.apache.org/confluence/display/GEODE/Geode+Command+to+replicate+region+data+from+one+site+to+another+connected+via+WAN with some modifications with respect to the initial proposal. The command will get the entries of a region in a WAN site and will put them in batches that will be sent by a gateway sender to a remote WAN site. * GEODE-9369: Remove comments added to geode-gfsh/src/test/resources/expected-pom.xml * GEODE-9369: Changes after review * GEODE-9369: Update with Kirk's review comments * GEODE-9369: Update with boglesby's review comments * GEODE-9369: Changes after boglesby's review * GEODE-9369: Updated with davebarnes97's review comments. * GEODE-9369: More changes after davebarnes97's review * GEODE-9369: Updated with DonalEvan's comments * GEODE-9369: Small refactoring: Use CompletableFuture instead of Callable + FutureTask * GEODE-9369: Fix race condition added in previous commit * GEODE-9369: Small change of re-review from DonalEvans * GEODE-9369: Fix esporadic test failures due to error log. * GEODE-9369: Changes required after rebasing to develop > Command to copy region entries from a WAN site to another. > -- > > Key: GEODE-9369 > URL: https://issues.apache.org/jira/browse/GEODE-9369 > Project: Geode > Issue Type: New Feature > Components: wan >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > As described in RFC: > [https://cwiki.apache.org/confluence/display/GEODE/Geode+Command+to+replicate+region+data+from+one+site+to+another+connected+via+WAN] > it is proposed to implement a command that copies the entries of a region in > a WAN site to the same region in another WAN site by using WAN replication. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9369) Command to copy region entries from a WAN site to another.
[ https://issues.apache.org/jira/browse/GEODE-9369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404214#comment-17404214 ] ASF subversion and git services commented on GEODE-9369: Commit c9d465b1e77dbc7bcc87eaea3522029530bb2b2b in geode's branch refs/heads/develop from Alberto Gomez [ https://gitbox.apache.org/repos/asf?p=geode.git;h=c9d465b ] GEODE-9369: Command to copy region entries from a WAN site to another (#6601) * GEODE-9369: Command to copy region entries from a WAN site to another The command has been implemented as proposed in https://cwiki.apache.org/confluence/display/GEODE/Geode+Command+to+replicate+region+data+from+one+site+to+another+connected+via+WAN with some modifications with respect to the initial proposal. The command will get the entries of a region in a WAN site and will put them in batches that will be sent by a gateway sender to a remote WAN site. * GEODE-9369: Remove comments added to geode-gfsh/src/test/resources/expected-pom.xml * GEODE-9369: Changes after review * GEODE-9369: Update with Kirk's review comments * GEODE-9369: Update with boglesby's review comments * GEODE-9369: Changes after boglesby's review * GEODE-9369: Updated with davebarnes97's review comments. * GEODE-9369: More changes after davebarnes97's review * GEODE-9369: Updated with DonalEvan's comments * GEODE-9369: Small refactoring: Use CompletableFuture instead of Callable + FutureTask * GEODE-9369: Fix race condition added in previous commit * GEODE-9369: Small change of re-review from DonalEvans * GEODE-9369: Fix esporadic test failures due to error log. * GEODE-9369: Changes required after rebasing to develop > Command to copy region entries from a WAN site to another. > -- > > Key: GEODE-9369 > URL: https://issues.apache.org/jira/browse/GEODE-9369 > Project: Geode > Issue Type: New Feature > Components: wan >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > As described in RFC: > [https://cwiki.apache.org/confluence/display/GEODE/Geode+Command+to+replicate+region+data+from+one+site+to+another+connected+via+WAN] > it is proposed to implement a command that copies the entries of a region in > a WAN site to the same region in another WAN site by using WAN replication. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9369) Command to copy region entries from a WAN site to another.
[ https://issues.apache.org/jira/browse/GEODE-9369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404225#comment-17404225 ] ASF subversion and git services commented on GEODE-9369: Commit c9d465b1e77dbc7bcc87eaea3522029530bb2b2b in geode's branch refs/heads/develop from Alberto Gomez [ https://gitbox.apache.org/repos/asf?p=geode.git;h=c9d465b ] GEODE-9369: Command to copy region entries from a WAN site to another (#6601) * GEODE-9369: Command to copy region entries from a WAN site to another The command has been implemented as proposed in https://cwiki.apache.org/confluence/display/GEODE/Geode+Command+to+replicate+region+data+from+one+site+to+another+connected+via+WAN with some modifications with respect to the initial proposal. The command will get the entries of a region in a WAN site and will put them in batches that will be sent by a gateway sender to a remote WAN site. * GEODE-9369: Remove comments added to geode-gfsh/src/test/resources/expected-pom.xml * GEODE-9369: Changes after review * GEODE-9369: Update with Kirk's review comments * GEODE-9369: Update with boglesby's review comments * GEODE-9369: Changes after boglesby's review * GEODE-9369: Updated with davebarnes97's review comments. * GEODE-9369: More changes after davebarnes97's review * GEODE-9369: Updated with DonalEvan's comments * GEODE-9369: Small refactoring: Use CompletableFuture instead of Callable + FutureTask * GEODE-9369: Fix race condition added in previous commit * GEODE-9369: Small change of re-review from DonalEvans * GEODE-9369: Fix esporadic test failures due to error log. * GEODE-9369: Changes required after rebasing to develop > Command to copy region entries from a WAN site to another. > -- > > Key: GEODE-9369 > URL: https://issues.apache.org/jira/browse/GEODE-9369 > Project: Geode > Issue Type: New Feature > Components: wan >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > As described in RFC: > [https://cwiki.apache.org/confluence/display/GEODE/Geode+Command+to+replicate+region+data+from+one+site+to+another+connected+via+WAN] > it is proposed to implement a command that copies the entries of a region in > a WAN site to the same region in another WAN site by using WAN replication. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9369) Command to copy region entries from a WAN site to another.
[ https://issues.apache.org/jira/browse/GEODE-9369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404222#comment-17404222 ] ASF subversion and git services commented on GEODE-9369: Commit c9d465b1e77dbc7bcc87eaea3522029530bb2b2b in geode's branch refs/heads/develop from Alberto Gomez [ https://gitbox.apache.org/repos/asf?p=geode.git;h=c9d465b ] GEODE-9369: Command to copy region entries from a WAN site to another (#6601) * GEODE-9369: Command to copy region entries from a WAN site to another The command has been implemented as proposed in https://cwiki.apache.org/confluence/display/GEODE/Geode+Command+to+replicate+region+data+from+one+site+to+another+connected+via+WAN with some modifications with respect to the initial proposal. The command will get the entries of a region in a WAN site and will put them in batches that will be sent by a gateway sender to a remote WAN site. * GEODE-9369: Remove comments added to geode-gfsh/src/test/resources/expected-pom.xml * GEODE-9369: Changes after review * GEODE-9369: Update with Kirk's review comments * GEODE-9369: Update with boglesby's review comments * GEODE-9369: Changes after boglesby's review * GEODE-9369: Updated with davebarnes97's review comments. * GEODE-9369: More changes after davebarnes97's review * GEODE-9369: Updated with DonalEvan's comments * GEODE-9369: Small refactoring: Use CompletableFuture instead of Callable + FutureTask * GEODE-9369: Fix race condition added in previous commit * GEODE-9369: Small change of re-review from DonalEvans * GEODE-9369: Fix esporadic test failures due to error log. * GEODE-9369: Changes required after rebasing to develop > Command to copy region entries from a WAN site to another. > -- > > Key: GEODE-9369 > URL: https://issues.apache.org/jira/browse/GEODE-9369 > Project: Geode > Issue Type: New Feature > Components: wan >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > As described in RFC: > [https://cwiki.apache.org/confluence/display/GEODE/Geode+Command+to+replicate+region+data+from+one+site+to+another+connected+via+WAN] > it is proposed to implement a command that copies the entries of a region in > a WAN site to the same region in another WAN site by using WAN replication. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9369) Command to copy region entries from a WAN site to another.
[ https://issues.apache.org/jira/browse/GEODE-9369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404219#comment-17404219 ] ASF subversion and git services commented on GEODE-9369: Commit c9d465b1e77dbc7bcc87eaea3522029530bb2b2b in geode's branch refs/heads/develop from Alberto Gomez [ https://gitbox.apache.org/repos/asf?p=geode.git;h=c9d465b ] GEODE-9369: Command to copy region entries from a WAN site to another (#6601) * GEODE-9369: Command to copy region entries from a WAN site to another The command has been implemented as proposed in https://cwiki.apache.org/confluence/display/GEODE/Geode+Command+to+replicate+region+data+from+one+site+to+another+connected+via+WAN with some modifications with respect to the initial proposal. The command will get the entries of a region in a WAN site and will put them in batches that will be sent by a gateway sender to a remote WAN site. * GEODE-9369: Remove comments added to geode-gfsh/src/test/resources/expected-pom.xml * GEODE-9369: Changes after review * GEODE-9369: Update with Kirk's review comments * GEODE-9369: Update with boglesby's review comments * GEODE-9369: Changes after boglesby's review * GEODE-9369: Updated with davebarnes97's review comments. * GEODE-9369: More changes after davebarnes97's review * GEODE-9369: Updated with DonalEvan's comments * GEODE-9369: Small refactoring: Use CompletableFuture instead of Callable + FutureTask * GEODE-9369: Fix race condition added in previous commit * GEODE-9369: Small change of re-review from DonalEvans * GEODE-9369: Fix esporadic test failures due to error log. * GEODE-9369: Changes required after rebasing to develop > Command to copy region entries from a WAN site to another. > -- > > Key: GEODE-9369 > URL: https://issues.apache.org/jira/browse/GEODE-9369 > Project: Geode > Issue Type: New Feature > Components: wan >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > As described in RFC: > [https://cwiki.apache.org/confluence/display/GEODE/Geode+Command+to+replicate+region+data+from+one+site+to+another+connected+via+WAN] > it is proposed to implement a command that copies the entries of a region in > a WAN site to the same region in another WAN site by using WAN replication. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9369) Command to copy region entries from a WAN site to another.
[ https://issues.apache.org/jira/browse/GEODE-9369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404217#comment-17404217 ] ASF subversion and git services commented on GEODE-9369: Commit c9d465b1e77dbc7bcc87eaea3522029530bb2b2b in geode's branch refs/heads/develop from Alberto Gomez [ https://gitbox.apache.org/repos/asf?p=geode.git;h=c9d465b ] GEODE-9369: Command to copy region entries from a WAN site to another (#6601) * GEODE-9369: Command to copy region entries from a WAN site to another The command has been implemented as proposed in https://cwiki.apache.org/confluence/display/GEODE/Geode+Command+to+replicate+region+data+from+one+site+to+another+connected+via+WAN with some modifications with respect to the initial proposal. The command will get the entries of a region in a WAN site and will put them in batches that will be sent by a gateway sender to a remote WAN site. * GEODE-9369: Remove comments added to geode-gfsh/src/test/resources/expected-pom.xml * GEODE-9369: Changes after review * GEODE-9369: Update with Kirk's review comments * GEODE-9369: Update with boglesby's review comments * GEODE-9369: Changes after boglesby's review * GEODE-9369: Updated with davebarnes97's review comments. * GEODE-9369: More changes after davebarnes97's review * GEODE-9369: Updated with DonalEvan's comments * GEODE-9369: Small refactoring: Use CompletableFuture instead of Callable + FutureTask * GEODE-9369: Fix race condition added in previous commit * GEODE-9369: Small change of re-review from DonalEvans * GEODE-9369: Fix esporadic test failures due to error log. * GEODE-9369: Changes required after rebasing to develop > Command to copy region entries from a WAN site to another. > -- > > Key: GEODE-9369 > URL: https://issues.apache.org/jira/browse/GEODE-9369 > Project: Geode > Issue Type: New Feature > Components: wan >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > As described in RFC: > [https://cwiki.apache.org/confluence/display/GEODE/Geode+Command+to+replicate+region+data+from+one+site+to+another+connected+via+WAN] > it is proposed to implement a command that copies the entries of a region in > a WAN site to the same region in another WAN site by using WAN replication. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9369) Command to copy region entries from a WAN site to another.
[ https://issues.apache.org/jira/browse/GEODE-9369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404211#comment-17404211 ] ASF subversion and git services commented on GEODE-9369: Commit c9d465b1e77dbc7bcc87eaea3522029530bb2b2b in geode's branch refs/heads/develop from Alberto Gomez [ https://gitbox.apache.org/repos/asf?p=geode.git;h=c9d465b ] GEODE-9369: Command to copy region entries from a WAN site to another (#6601) * GEODE-9369: Command to copy region entries from a WAN site to another The command has been implemented as proposed in https://cwiki.apache.org/confluence/display/GEODE/Geode+Command+to+replicate+region+data+from+one+site+to+another+connected+via+WAN with some modifications with respect to the initial proposal. The command will get the entries of a region in a WAN site and will put them in batches that will be sent by a gateway sender to a remote WAN site. * GEODE-9369: Remove comments added to geode-gfsh/src/test/resources/expected-pom.xml * GEODE-9369: Changes after review * GEODE-9369: Update with Kirk's review comments * GEODE-9369: Update with boglesby's review comments * GEODE-9369: Changes after boglesby's review * GEODE-9369: Updated with davebarnes97's review comments. * GEODE-9369: More changes after davebarnes97's review * GEODE-9369: Updated with DonalEvan's comments * GEODE-9369: Small refactoring: Use CompletableFuture instead of Callable + FutureTask * GEODE-9369: Fix race condition added in previous commit * GEODE-9369: Small change of re-review from DonalEvans * GEODE-9369: Fix esporadic test failures due to error log. * GEODE-9369: Changes required after rebasing to develop > Command to copy region entries from a WAN site to another. > -- > > Key: GEODE-9369 > URL: https://issues.apache.org/jira/browse/GEODE-9369 > Project: Geode > Issue Type: New Feature > Components: wan >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > As described in RFC: > [https://cwiki.apache.org/confluence/display/GEODE/Geode+Command+to+replicate+region+data+from+one+site+to+another+connected+via+WAN] > it is proposed to implement a command that copies the entries of a region in > a WAN site to the same region in another WAN site by using WAN replication. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9369) Command to copy region entries from a WAN site to another.
[ https://issues.apache.org/jira/browse/GEODE-9369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404226#comment-17404226 ] ASF subversion and git services commented on GEODE-9369: Commit c9d465b1e77dbc7bcc87eaea3522029530bb2b2b in geode's branch refs/heads/develop from Alberto Gomez [ https://gitbox.apache.org/repos/asf?p=geode.git;h=c9d465b ] GEODE-9369: Command to copy region entries from a WAN site to another (#6601) * GEODE-9369: Command to copy region entries from a WAN site to another The command has been implemented as proposed in https://cwiki.apache.org/confluence/display/GEODE/Geode+Command+to+replicate+region+data+from+one+site+to+another+connected+via+WAN with some modifications with respect to the initial proposal. The command will get the entries of a region in a WAN site and will put them in batches that will be sent by a gateway sender to a remote WAN site. * GEODE-9369: Remove comments added to geode-gfsh/src/test/resources/expected-pom.xml * GEODE-9369: Changes after review * GEODE-9369: Update with Kirk's review comments * GEODE-9369: Update with boglesby's review comments * GEODE-9369: Changes after boglesby's review * GEODE-9369: Updated with davebarnes97's review comments. * GEODE-9369: More changes after davebarnes97's review * GEODE-9369: Updated with DonalEvan's comments * GEODE-9369: Small refactoring: Use CompletableFuture instead of Callable + FutureTask * GEODE-9369: Fix race condition added in previous commit * GEODE-9369: Small change of re-review from DonalEvans * GEODE-9369: Fix esporadic test failures due to error log. * GEODE-9369: Changes required after rebasing to develop > Command to copy region entries from a WAN site to another. > -- > > Key: GEODE-9369 > URL: https://issues.apache.org/jira/browse/GEODE-9369 > Project: Geode > Issue Type: New Feature > Components: wan >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > As described in RFC: > [https://cwiki.apache.org/confluence/display/GEODE/Geode+Command+to+replicate+region+data+from+one+site+to+another+connected+via+WAN] > it is proposed to implement a command that copies the entries of a region in > a WAN site to the same region in another WAN site by using WAN replication. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9369) Command to copy region entries from a WAN site to another.
[ https://issues.apache.org/jira/browse/GEODE-9369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404213#comment-17404213 ] ASF subversion and git services commented on GEODE-9369: Commit c9d465b1e77dbc7bcc87eaea3522029530bb2b2b in geode's branch refs/heads/develop from Alberto Gomez [ https://gitbox.apache.org/repos/asf?p=geode.git;h=c9d465b ] GEODE-9369: Command to copy region entries from a WAN site to another (#6601) * GEODE-9369: Command to copy region entries from a WAN site to another The command has been implemented as proposed in https://cwiki.apache.org/confluence/display/GEODE/Geode+Command+to+replicate+region+data+from+one+site+to+another+connected+via+WAN with some modifications with respect to the initial proposal. The command will get the entries of a region in a WAN site and will put them in batches that will be sent by a gateway sender to a remote WAN site. * GEODE-9369: Remove comments added to geode-gfsh/src/test/resources/expected-pom.xml * GEODE-9369: Changes after review * GEODE-9369: Update with Kirk's review comments * GEODE-9369: Update with boglesby's review comments * GEODE-9369: Changes after boglesby's review * GEODE-9369: Updated with davebarnes97's review comments. * GEODE-9369: More changes after davebarnes97's review * GEODE-9369: Updated with DonalEvan's comments * GEODE-9369: Small refactoring: Use CompletableFuture instead of Callable + FutureTask * GEODE-9369: Fix race condition added in previous commit * GEODE-9369: Small change of re-review from DonalEvans * GEODE-9369: Fix esporadic test failures due to error log. * GEODE-9369: Changes required after rebasing to develop > Command to copy region entries from a WAN site to another. > -- > > Key: GEODE-9369 > URL: https://issues.apache.org/jira/browse/GEODE-9369 > Project: Geode > Issue Type: New Feature > Components: wan >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > As described in RFC: > [https://cwiki.apache.org/confluence/display/GEODE/Geode+Command+to+replicate+region+data+from+one+site+to+another+connected+via+WAN] > it is proposed to implement a command that copies the entries of a region in > a WAN site to the same region in another WAN site by using WAN replication. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9369) Command to copy region entries from a WAN site to another.
[ https://issues.apache.org/jira/browse/GEODE-9369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Gomez resolved GEODE-9369. -- Fix Version/s: 1.15.0 Resolution: Fixed > Command to copy region entries from a WAN site to another. > -- > > Key: GEODE-9369 > URL: https://issues.apache.org/jira/browse/GEODE-9369 > Project: Geode > Issue Type: New Feature > Components: wan >Reporter: Alberto Gomez >Assignee: Alberto Gomez >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > As described in RFC: > [https://cwiki.apache.org/confluence/display/GEODE/Geode+Command+to+replicate+region+data+from+one+site+to+another+connected+via+WAN] > it is proposed to implement a command that copies the entries of a region in > a WAN site to the same region in another WAN site by using WAN replication. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
