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.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
