[
https://issues.apache.org/jira/browse/GEODE-352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14957155#comment-14957155
]
ASF subversion and git services commented on GEODE-352:
-------------------------------------------------------
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.
> PRClientServerRegionFunctionExecutionSelectorNoSingleHopDUnitTest.testserverMultiKeyExecution_byInlineFunction
> fails intermittently with suspect string
> -------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: GEODE-352
> URL: https://issues.apache.org/jira/browse/GEODE-352
> Project: Geode
> Issue Type: Bug
> Reporter: Darrel Schneider
> Assignee: Dan Smith
> Labels: CI
>
> Failure was on a private build.
> {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 2039
> java.net.SocketTimeoutException: Read timed out
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
