[ https://issues.apache.org/jira/browse/GEODE-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16347830#comment-16347830 ]
ASF subversion and git services commented on GEODE-3948: -------------------------------------------------------- Commit e093db0ff293e078888f1ab6700adfa633dd93bf in geode's branch refs/heads/feature/GEODE-3948 from [~bschuchardt] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=e093db0 ] GEODE-3948 Improve CQ performance under flaky network conditions Addressing review comments. > 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: cq, messaging > Reporter: Galen O'Sullivan > Assignee: Galen O'Sullivan > Priority: Minor > Labels: pull-request-available > Time Spent: 1.5h > 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)