[GEODE-8616] ClientServerCacheOperationDUnitTest > largeObjectPutWithReadTimeoutThrowsException fails with ServerConnectivityException : Pool unexpected socket timed out on client

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.12.1, 1.13.7, 1.14.3, 1.15.0
• Fix Version/s: 1.15.0
• Labels: GeodeOperationAPI flaky-test pull-request-available testing
• Assignee: Nabarun Nag
• Reporter: Donal Evans
• Created: 15/Oct/20 17:31
• Updated: 22/Jun/22 20:46
• Resolved: 25/Jan/22 17:34

Description

> Task :geode-core:distributedTest

org.apache.geode.cache30.ClientServerCacheOperationDUnitTest > largeObjectPutWithReadTimeoutThrowsException FAILED
    org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.cache30.ClientServerCacheOperationDUnitTest$$Lambda$177/0x0000000100b52040.run in VM 2 running on Host c1346ab7b3e3 with 4 VMs
        at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)
        at org.apache.geode.test.dunit.VM.invoke(VM.java:437)
        at org.apache.geode.cache30.ClientServerCacheOperationDUnitTest.largeObjectPutWithReadTimeoutThrowsException(ClientServerCacheOperationDUnitTest.java:117)

        Caused by:
        org.apache.geode.cache.client.ServerConnectivityException: Pool unexpected socket timed out on client connection=Pooled Connection to c1346ab7b3e3:35437: Connection[DESTROYED]). Server unreachable: could not connect after 1 attempts
            at org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:659)
            at org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:501)
            at org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:153)
            at org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:108)
            at org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:774)
            at org.apache.geode.cache.client.internal.GetOp.execute(GetOp.java:91)
            at org.apache.geode.cache.client.internal.ServerRegionProxy.get(ServerRegionProxy.java:116)
            at org.apache.geode.internal.cache.LocalRegion.findObjectInSystem(LocalRegion.java:2795)
            at org.apache.geode.internal.cache.LocalRegion.getObject(LocalRegion.java:1472)
            at org.apache.geode.internal.cache.LocalRegion.nonTxnFindObject(LocalRegion.java:1445)
            at org.apache.geode.internal.cache.LocalRegionDataView.findObject(LocalRegionDataView.java:196)
            at org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1382)
            at org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1321)
            at org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1306)
            at org.apache.geode.internal.cache.AbstractRegion.get(AbstractRegion.java:436)
            at org.apache.geode.cache30.ClientServerCacheOperationDUnitTest.lambda$largeObjectPutWithReadTimeoutThrowsException$3ab01cf6$2(ClientServerCacheOperationDUnitTest.java:120)

=============== Test Results URI =================
http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.1-build.0106/test-results/distributedTest/1601514101/
=========================================

Test report artifacts from this job are available at:

http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.1-build.0106/test-artifacts/1601514101/distributedtestfiles-OpenJDK11-1.12.1-build.0106.tgz

This is a flaky failure.

Issue Links

• links to: GitHub Pull Request #7301