You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Brian Rowe (JIRA)" <ji...@apache.org> on 2018/10/19 17:05:00 UTC
[jira] [Resolved] (GEODE-632) SUPERFLAKY:
DistributedRegionFunctionExecutionDUnitTest.testDistributedRegionFunctionExecutionOnDataPolicyEmpty_ClientServer_NoLastResult
[ https://issues.apache.org/jira/browse/GEODE-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Rowe resolved GEODE-632.
------------------------------
Resolution: Cannot Reproduce
Unable to reproduce in 65,000 runs...I suspect that this may have been fixed by one of the other socket or connection fixes that have gone in recently.
> SUPERFLAKY: DistributedRegionFunctionExecutionDUnitTest.testDistributedRegionFunctionExecutionOnDataPolicyEmpty_ClientServer_NoLastResult
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: GEODE-632
> URL: https://issues.apache.org/jira/browse/GEODE-632
> Project: Geode
> Issue Type: Bug
> Components: functions
> Reporter: Darrel Schneider
> Assignee: Brian Rowe
> Priority: Major
> Labels: CI, Flaky, swat
>
> git rev 9283282c64076c5f8e599f3d47895f3c48e205e8 build #813
> 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 4649
> [fatal 2015/12/06 15:02:06.760 PST <Pooled High Priority Message Processor 2> tid=0x233b] Uncaught exception processing com.gemstone.gemfire.internal.cache.FunctionStreamingReplyMessage(processorId=10999 from cc4-rh6(25294)<ec><v1344>:1027;msgNum 0;lastMsg=false)
> com.gemstone.gemfire.cache.execute.FunctionException: IOException while sending the result chunk to client
> at com.gemstone.gemfire.internal.cache.execute.ServerToClientFunctionResultSender65.sendResult(ServerToClientFunctionResultSender65.java:247)
> at com.gemstone.gemfire.internal.cache.execute.DistributedRegionFunctionResultSender.sendResult(DistributedRegionFunctionResultSender.java:204)
> at com.gemstone.gemfire.internal.cache.execute.StreamingFunctionOperation.processData(StreamingFunctionOperation.java:93)
> at com.gemstone.gemfire.internal.cache.execute.FunctionStreamingResultCollector.process(FunctionStreamingResultCollector.java:541)
> at com.gemstone.gemfire.distributed.internal.ReplyMessage.process(ReplyMessage.java:231)
> at com.gemstone.gemfire.distributed.internal.ReplyMessage.dmProcess(ReplyMessage.java:212)
> at com.gemstone.gemfire.distributed.internal.ReplyMessage.process(ReplyMessage.java:201)
> at com.gemstone.gemfire.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:380)
> at com.gemstone.gemfire.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:451)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at com.gemstone.gemfire.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:658)
> at com.gemstone.gemfire.distributed.internal.DistributionManager$5$1.run(DistributionManager.java:969)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.net.SocketException: Socket closed
> at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:116)
> at java.net.SocketOutputStream.write(SocketOutputStream.java:153)
> at com.gemstone.gemfire.internal.cache.tier.sockets.Message.flushBuffer(Message.java:668)
> at com.gemstone.gemfire.internal.cache.tier.sockets.ChunkedMessage.sendHeader(ChunkedMessage.java:295)
> at com.gemstone.gemfire.internal.cache.execute.ServerToClientFunctionResultSender.sendHeader(ServerToClientFunctionResultSender.java:271)
> at com.gemstone.gemfire.internal.cache.execute.ServerToClientFunctionResultSender65.sendResult(ServerToClientFunctionResultSender65.java:228)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)