You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Darrel Schneider (JIRA)" <ji...@apache.org> on 2015/09/22 20:30:05 UTC
[jira] [Created] (GEODE-355) Intermittent suspect string failure of
PRClientServerRegionFunctionExecutionSelectorNoSingleHopDUnitTest.testserverMultiKeyExecution_SocektTimeOut
Darrel Schneider created GEODE-355:
--------------------------------------
Summary: 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
Priority: Minor
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)