[ https://issues.apache.org/jira/browse/GEODE-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15925035#comment-15925035 ]
ASF GitHub Bot commented on GEODE-2657: --------------------------------------- Github user dgkimura commented on the issue: https://github.com/apache/geode-native/pull/54 @echobravopapa We're only human. Our unittest didn't catch it originally because the output that's written to DataOutput in the constructor is the same with/without this variable set. It's likely when the message is sent that client checks this variable and performs some magic. I'm guessing our integration-tests that cover this aren't running. Else we might have had a chance. > Execute Region Function sends incorrect message format > ------------------------------------------------------ > > Key: GEODE-2657 > URL: https://issues.apache.org/jira/browse/GEODE-2657 > Project: Geode > Issue Type: Bug > Components: native client > Reporter: David Kimura > > `TcrMessageExecuteRegionFunction` is missing a call to set `m_hasResults`. > This causes the message response to be parsed synchronously and not > asynchronously chunked. The synchronous parser does not support this message > type and it barfs. -- This message was sent by Atlassian JIRA (v6.3.15#6346)