You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Anthony Baker (JIRA)" <ji...@apache.org> on 2018/11/07 23:24:17 UTC

[jira] [Resolved] (GEODE-4167) CI Failure: PRClientServerRegionFunctionExecutionFailoverDUnitTest.testOnRegionFailoverWithTwoServerDownHA

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

Anthony Baker resolved GEODE-4167.
----------------------------------
    Resolution: Cannot Reproduce

This issue has either failed to reproduce or been fixed systemically elsewhere (e.g. improving port selection and timeouts).  Closing but please reopen if needed.

> CI Failure: PRClientServerRegionFunctionExecutionFailoverDUnitTest.testOnRegionFailoverWithTwoServerDownHA
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-4167
>                 URL: https://issues.apache.org/jira/browse/GEODE-4167
>             Project: Geode
>          Issue Type: Bug
>            Reporter: Brian Rowe
>            Priority: Major
>
> org.apache.geode.internal.cache.execute.PRClientServerRegionFunctionExecutionFailoverDUnitTest > testOnRegionFailoverWithTwoServerDownHA FAILED
>     org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.internal.cache.execute.PRClientServerRegionFunctionExecutionFailoverDUnitTest$$Lambda$139/157295940.run in VM 3 running on Host c1805723ab71 with 4 VMs
>         at org.apache.geode.test.dunit.VM.invoke(VM.java:393)
>         at org.apache.geode.test.dunit.VM.invoke(VM.java:363)
>         at org.apache.geode.test.dunit.VM.invoke(VM.java:308)
>         at org.apache.geode.internal.cache.execute.PRClientServerRegionFunctionExecutionFailoverDUnitTest.testOnRegionFailoverWithTwoServerDownHA(PRClientServerRegionFunctionExecutionFailoverDUnitTest.java:179)
>         Caused by:
>         org.apache.geode.cache.execute.FunctionException: org.apache.geode.cache.client.ServerConnectivityException: Pool unexpected closed socket on server connection=Pooled Connection to c1805723ab71:29590: Connection[c1805723ab71:29590]@2123842241). Server unreachable: could not connect after 1 attempts
>             at org.apache.geode.internal.cache.execute.ServerRegionFunctionExecutor.executeOnServer(ServerRegionFunctionExecutor.java:216)
>             at org.apache.geode.internal.cache.execute.ServerRegionFunctionExecutor.executeFunction(ServerRegionFunctionExecutor.java:160)
>             at org.apache.geode.internal.cache.execute.AbstractExecution.execute(AbstractExecution.java:396)
>             at org.apache.geode.internal.cache.execute.PRClientServerRegionFunctionExecutionDUnitTest.execute(PRClientServerRegionFunctionExecutionDUnitTest.java:1525)
>             at org.apache.geode.internal.cache.execute.PRClientServerRegionFunctionExecutionDUnitTest.regionExecutionHATwoServerDown(PRClientServerRegionFunctionExecutionDUnitTest.java:540)
>             at org.apache.geode.internal.cache.execute.PRClientServerRegionFunctionExecutionFailoverDUnitTest.lambda$testOnRegionFailoverWithTwoServerDownHA$c356a657$1(PRClientServerRegionFunctionExecutionFailoverDUnitTest.java:180)
>             Caused by:
>             org.apache.geode.cache.client.ServerConnectivityException: Pool unexpected closed socket on server connection=Pooled Connection to c1805723ab71:29590: Connection[c1805723ab71:29590]@2123842241). Server unreachable: could not connect after 1 attempts
>                 at org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:786)
>                 at org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:611)
>                 at org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:168)
>                 at org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:788)
>                 at org.apache.geode.cache.client.internal.ExecuteRegionFunctionOp.reexecute(ExecuteRegionFunctionOp.java:223)
>                 at org.apache.geode.cache.client.internal.ExecuteRegionFunctionOp.execute(ExecuteRegionFunctionOp.java:134)
>                 at org.apache.geode.cache.client.internal.ServerRegionProxy.executeFunction(ServerRegionProxy.java:715)
>                 at org.apache.geode.internal.cache.execute.ServerRegionFunctionExecutor.executeOnServer(ServerRegionFunctionExecutor.java:208)
>                 ... 5 more
>                 Caused by:
>                 java.io.EOFException: The connection has been reset while reading the header
>                     at org.apache.geode.internal.cache.tier.sockets.Message.fetchHeader(Message.java:690)
>                     at org.apache.geode.internal.cache.tier.sockets.ChunkedMessage.readHeader(ChunkedMessage.java:198)
>                     at org.apache.geode.cache.client.internal.ExecuteRegionFunctionOp$ExecuteRegionFunctionOpImpl.processResponse(ExecuteRegionFunctionOp.java:497)
>                     at org.apache.geode.cache.client.internal.AbstractOp.processResponse(AbstractOp.java:228)
>                     at org.apache.geode.cache.client.internal.AbstractOp.attemptReadResponse(AbstractOp.java:201)
>                     at org.apache.geode.cache.client.internal.AbstractOp.attempt(AbstractOp.java:392)
>                     at org.apache.geode.cache.client.internal.ConnectionImpl.execute(ConnectionImpl.java:275)
>                     at org.apache.geode.cache.client.internal.pooling.PooledConnection.execute(PooledConnection.java:332)
>                     at org.apache.geode.cache.client.internal.OpExecutorImpl.executeWithPossibleReAuthentication(OpExecutorImpl.java:888)
>                     at org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:159)
>                     ... 10 more
> There are a couple of other bugs for this test that have been resolved, but this doesn't appear to be a reemergence of either GEODE-971 or GEODE-705.
> Failure occurred in concourse DistributedTest run based on git rev. 20f0d99ebc449a5feba4a8b2a4a22d758f8d086e.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)