[
https://issues.apache.org/jira/browse/GEODE-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15073201#comment-15073201
]
ASF subversion and git services commented on GEODE-355:
-------------------------------------------------------
Commit 2a21b70477123e679cbb76c8ffa07e44b6e45e6c in incubator-geode's branch
refs/heads/feature/GEODE-217 from [~bschuchardt]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=2a21b70 ]
Fix for suspect string causing a number of CI failures
During shutdown it's possible for the DirectChannel communication service
to throw a ConnectExceptions containing a ShunnedMemberException for one
or more members. These indicate that the message couldn't be sent, but this
is expected behavior and the ShunnedMemberExceptions can be ignored.
This fixes GEODE-355, GEODE-682, GEODE-683, GEODE-684, GEODE-685, GEODE-687,
GEODE-689, GEODE-691, GEODE-702 and GEODE-703.
> 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
> 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)
