geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-355) Intermittent suspect string failure of PRClientServerRegionFunctionExecutionSelectorNoSingleHopDUnitTest.testserverMultiKeyExecution_SocektTimeOut
Date Wed, 14 Oct 2015 16:08:07 GMT

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

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

Commit f50ca04c9e8f30f290851a3cd419f2a834b5c6e2 in incubator-geode's branch refs/heads/feature/GEODE-77
from [~upthewaterspout]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=f50ca04 ]

GEODE-352: Ingoring SocketTimeoutException in dunit runs

I believe this may also be the root cause of GEODE-270, GEODE-355,
GEODE-298, and GEODE-326.

The problem is that during tearDown, we start shutting down the cache
servers first, resulting in connectivity errors on the client.


> Intermittent suspect string failure of PRClientServerRegionFunctionExecutionSelectorNoSingleHopDUnitTest.testserverMultiKeyExecution_SocektTimeOut
> --------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-355
>                 URL: https://issues.apache.org/jira/browse/GEODE-355
>             Project: Geode
>          Issue Type: Bug
>          Components: client/server
>            Reporter: Darrel Schneider
>            Assignee: Anilkumar Gingade
>            Priority: Minor
>              Labels: CI
>
> PRClientServerRegionFunctionExecutionSelectorNoSingleHopDUnitTest.testserverMultiKeyExecution_SocektTimeOut
may fail with:
> {code}
> java.lang.AssertionError: Suspicious strings were written to the log during this run.
> Fix the strings or use DistributedTestCase.addExpectedException to ignore.
> -----------------------------------------------------------------------
> Found suspect string in log4j at line 3015
> java.net.SocketTimeoutException: Read timed out
> {code}
> The exception:
> {code}
> [vm_3][warn 2015/09/20 17:38:44.852 PDT <poolTimer-PRClientServerTestBase-2> tid=0x37e0]
Could not connect to: cc2-rh6.gemstone.com:21380
> [vm_3]java.net.SocketTimeoutException: Read timed out
> [vm_3]	at java.net.SocketInputStream.socketRead0(Native Method)
> [vm_3]	at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
> [vm_3]	at java.net.SocketInputStream.read(SocketInputStream.java:170)
> [vm_3]	at java.net.SocketInputStream.read(SocketInputStream.java:141)
> [vm_3]	at java.net.SocketInputStream.read(SocketInputStream.java:223)
> [vm_3]	at java.io.DataInputStream.readByte(DataInputStream.java:265)
> [vm_3]	at com.gemstone.gemfire.internal.cache.tier.sockets.HandShake.greet(HandShake.java:1291)
> [vm_3]	at com.gemstone.gemfire.cache.client.internal.ConnectionImpl.connect(ConnectionImpl.java:127)
> [vm_3]	at com.gemstone.gemfire.cache.client.internal.ConnectionFactoryImpl.createClientToServerConnection(ConnectionFactoryImpl.java:117)
> [vm_3]	at com.gemstone.gemfire.cache.client.internal.ConnectionFactoryImpl.createClientToServerConnection(ConnectionFactoryImpl.java:233)
> [vm_3]	at com.gemstone.gemfire.cache.client.internal.pooling.ConnectionManagerImpl.prefillConnection(ConnectionManagerImpl.java:795)
> [vm_3]	at com.gemstone.gemfire.cache.client.internal.pooling.ConnectionManagerImpl.prefill(ConnectionManagerImpl.java:738)
> [vm_3]	at com.gemstone.gemfire.cache.client.internal.pooling.ConnectionManagerImpl$PrefillConnectionsTask.run2(ConnectionManagerImpl.java:889)
> [vm_3]	at com.gemstone.gemfire.cache.client.internal.PoolImpl$PoolTask.run(PoolImpl.java:1250)
> [vm_3]	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [vm_3]	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [vm_3]	at java.lang.Thread.run(Thread.java:745)
> {code}
> I also see this test adds SocketTimeoutException to its expected exceptions but it was
not added before the above call stack



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message