[ https://issues.apache.org/jira/browse/GEODE-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16815827#comment-16815827 ]
ASF subversion and git services commented on GEODE-3948: -------------------------------------------------------- Commit 7536f2e56a73610c1c694b4c9648107405ed735a in geode's branch refs/heads/feature/GEODE-3948b from Bruce Schuchardt [ https://gitbox.apache.org/repos/asf?p=geode.git;h=7536f2e ] GEODE-3948 fixing handling of sotimeout in Message.receive() Changes made for GEODE-3948 caused the Message.receive() method to block indefinitely waiting for a response. That wasn't the intent - it should honor the current setting of sotimeout. > Improve CQ performance under flaky network conditions > ----------------------------------------------------- > > Key: GEODE-3948 > URL: https://issues.apache.org/jira/browse/GEODE-3948 > Project: Geode > Issue Type: Improvement > Components: docs > Reporter: Galen O'Sullivan > Assignee: Bruce Schuchardt > Priority: Minor > Labels: pull-request-available > Fix For: 1.5.0 > > Time Spent: 3h > Remaining Estimate: 0h > > Client CQ connections occasionally stop receiving messages and become blocked > indefinitely. > This can be caused by a server that hangs or dies without sending a close > message, or by some firewalls. > The client already gets ping messages from the server, but currently ignores > them. Let's use those messages to detect a failed connection and close it. > Probably the client should follow the same logic and send ping messages if it > has sent no acks for a while, so that the server can also detect and close a > broken connection. > The timeout could be specified as a number and time interval, the ping > interval and the number of missed pings after which to fail. -- This message was sent by Atlassian JIRA (v7.6.3#76005)