[
https://issues.apache.org/jira/browse/GEODE-3082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16167097#comment-16167097
]
ASF subversion and git services commented on GEODE-3082:
--------------------------------------------------------
Commit b31de81a8c19c61ad27a2ab803073214050db154 in geode's branch
refs/heads/develop from [~amurmann]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=b31de81 ]
GEODE-3082 Integrate GenericProtocolServerConnection with ClientHealthMonitor.
1. Now GenericProtocolServerConnection creates ClientProxyMembershipId.
2. ClientHealthMonitor gets notified about pings
3. added test where CHM closes the connection.
4. added test where CHM doesn't close the connection
This currently results in every connetion being tracked as a separate
client.
> Client Health Monitor should be able to manage new protocol client connections
> ------------------------------------------------------------------------------
>
> Key: GEODE-3082
> URL: https://issues.apache.org/jira/browse/GEODE-3082
> Project: Geode
> Issue Type: Sub-task
> Components: client/server
> Reporter: Galen O'Sullivan
>
> As a user of a Geode grid, I need the Client Health Monitor to effectively
> manage my client connections, perhaps removing unresponsive clients
> (depending on my config).
> Ensure new protocol connections are managed correctly by Client Health
> Monitor.
> Specifically:
> {{ClientHealthMonitor}} keeps track of {{ServerConnection}}s, makes sure that
> they are healthy, and sometimes kills them. Make sure that
> {{NewClientServerConnection}} registers correctly with
> {{ClientHealthMonitor}} and unregisters correctly when we shutdown. Make sure
> that we let it manage us correctly.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
