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

ASF subversion and git services commented on GEODE-4178:
--------------------------------------------------------

Commit cdde35a6de01ced9e276c18783582431c172f221 in geode's branch 
refs/heads/develop from [~bschuchardt]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=cdde35a ]

GEODE-4178 ClientServerMiscDUnitTest.testOnSeverMethodsWithCachingProxyClientHA 
failure

This goofy test was setting a 1 second read-timeout and had only one server.
Our test JVMs have frequent GC cycles that can easily last over one second.

I could easily reproduce the failure by adding a cache writer on the server
that paused for a couple of seconds.

I've increased the read-timeout to 5 seconds.  It could be set to a longer
interval if this isn't enough.


> Failure from 
> ClientServerMiscDUnitTest.testOnSeverMethodsWithCachingProxyClientHA
> ---------------------------------------------------------------------------------
>
>                 Key: GEODE-4178
>                 URL: https://issues.apache.org/jira/browse/GEODE-4178
>             Project: Geode
>          Issue Type: Bug
>          Components: client/server
>            Reporter: Dan Smith
>
> This test failed in a precheckin run:
> {noformat}
> org.apache.geode.internal.cache.tier.sockets.ClientServerMiscDUnitTest > 
> testOnSeverMethodsWithCachingProxyClientHA FAILED
>     org.apache.geode.cache.client.ServerConnectivityException: Pool 
> unexpected socket timed out on client connection=Pooled Connection to 
> cdcef3a9980a:20441: Connection[cdcef3a9980a:20441]@1092101079 attempt=2). 
> Server unreachable: could not connect after 2 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:175)
>         at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:116)
>         at 
> org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:774)
>         at org.apache.geode.cache.client.internal.PutOp.execute(PutOp.java:91)
>         at 
> org.apache.geode.cache.client.internal.ServerRegionProxy.put(ServerRegionProxy.java:159)
>         at 
> org.apache.geode.internal.cache.LocalRegion.serverPut(LocalRegion.java:3004)
>         at 
> org.apache.geode.internal.cache.DistributedRegion.cacheWriteBeforePut(DistributedRegion.java:2614)
>         at 
> org.apache.geode.internal.cache.AbstractRegionMap.invokeCacheWriter(AbstractRegionMap.java:3069)
>         at 
> org.apache.geode.internal.cache.AbstractRegionMap.basicPut(AbstractRegionMap.java:2828)
>         at 
> org.apache.geode.internal.cache.LocalRegion.virtualPut(LocalRegion.java:5622)
>         at 
> org.apache.geode.internal.cache.DistributedRegion.virtualPut(DistributedRegion.java:369)
>         at 
> org.apache.geode.internal.cache.LocalRegionDataView.putEntry(LocalRegionDataView.java:152)
>         at 
> org.apache.geode.internal.cache.LocalRegion.basicPut(LocalRegion.java:5051)
>         at 
> org.apache.geode.internal.cache.LocalRegion.validatedPut(LocalRegion.java:1583)
>         at 
> org.apache.geode.internal.cache.LocalRegion.put(LocalRegion.java:1570)
>         at 
> org.apache.geode.internal.cache.AbstractRegion.put(AbstractRegion.java:325)
>         at 
> org.apache.geode.internal.cache.tier.sockets.ClientServerMiscDUnitTest.putIntoRegion(ClientServerMiscDUnitTest.java:1445)
>         at 
> org.apache.geode.internal.cache.tier.sockets.ClientServerMiscDUnitTest.testOnServerMothods(ClientServerMiscDUnitTest.java:1423)
>         at 
> org.apache.geode.internal.cache.tier.sockets.ClientServerMiscDUnitTest.testOnSeverMethodsWithCachingProxyClientHA(ClientServerMiscDUnitTest.java:1398)
> {noformat}
> Looking at the code, it looks like it just has a low read timeout of 1 second 
> in _createClientCache. So on a slow system this test could just timeout and 
> throw this error. We should up the timeout.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to