[
https://issues.apache.org/jira/browse/GEODE-8394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17172570#comment-17172570
]
ASF GitHub Bot commented on GEODE-8394:
---------------------------------------
agingade commented on a change in pull request #5424:
URL: https://github.com/apache/geode/pull/5424#discussion_r466584837
##########
File path:
geode-core/src/distributedTest/java/org/apache/geode/cache30/ClientServerCacheOperationDUnitTest.java
##########
@@ -0,0 +1,200 @@
+/*
+ * 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.
+ */
+package org.apache.geode.cache30;
+
+import static org.apache.geode.cache.RegionShortcut.REPLICATE;
+import static org.assertj.core.api.Assertions.assertThat;
+import static org.assertj.core.api.Assertions.assertThatThrownBy;
+
+import java.io.IOException;
+import java.io.Serializable;
+import java.util.ArrayList;
+import java.util.List;
+
+import org.junit.Rule;
+import org.junit.Test;
+import org.junit.experimental.categories.Category;
+
+import org.apache.geode.cache.Region;
+import org.apache.geode.cache.RegionFactory;
+import org.apache.geode.cache.client.ClientRegionShortcut;
+import org.apache.geode.cache.client.Pool;
+import org.apache.geode.cache.client.PoolManager;
+import org.apache.geode.cache.client.ServerConnectivityException;
+import org.apache.geode.cache.server.CacheServer;
+import org.apache.geode.test.dunit.DistributedTestUtils;
+import org.apache.geode.test.dunit.VM;
+import org.apache.geode.test.dunit.rules.CacheRule;
+import org.apache.geode.test.dunit.rules.ClientCacheRule;
+import org.apache.geode.test.dunit.rules.DistributedRule;
+import org.apache.geode.test.junit.categories.ClientServerTest;
+
+@Category({ClientServerTest.class})
+public class ClientServerCacheOperationDUnitTest implements Serializable {
Review comment:
It was the test used to reproduce the original issue and test the fix.
If you can see it has dependency on environment and shows flaky-ness...With
adjusting the time; it is more of becoming a test for large object.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
> Client sends partial data during retry
> --------------------------------------
>
> Key: GEODE-8394
> URL: https://issues.apache.org/jira/browse/GEODE-8394
> Project: Geode
> Issue Type: Bug
> Components: client/server
> Affects Versions: 1.14.0
> Reporter: Anilkumar Gingade
> Assignee: Anilkumar Gingade
> Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
>
> When executing the command, java client sends the command in the form of
> message (Parts). If there is a failure during the send, it retries number of
> times based on the retry-attempt setting.
> If there is a failure in the first attempt due to Exception (IOException,
> EOFException - read timeout); during the second attempt the client is sending
> partial data, instead of the complete data.
> This could be reproduced by setting a small read-timeout and large object
> (Put).
> Because of this, the put from client succeeds by creating partial data on the
> server cache. Since the data is stored in serialized form, there is no
> exception thrown during put() operation, giving an impression that put
> operation is successful.
> The workaround for now is to have large read-timeout setting; while trying to
> send a large object.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
