[ 
https://issues.apache.org/jira/browse/GEODE-8683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17227646#comment-17227646
 ] 

ASF subversion and git services commented on GEODE-8683:
--------------------------------------------------------

Commit c0689791876c2fda1e5fb4b1337daae3cbddcbe8 in geode's branch 
refs/heads/develop from Alberto Gomez
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=c068979 ]

GEODE-8683: Honor maximum-time-between-pings in gateway receiver (#5701)

The maximum-time-between-pings set when creating a gateway receiver
was not honored because the ClientHealthMonitor, that is the singleton
class monitoring all clients supported just one value for maximum
time between pings for all clients. This value is set
when the server in which the receiver is running is started
and when the gateway receiver provides a different value
it is ignored.

With this fix, it is allowed to have different values
for maximum-time-between-clients for different clients
as the value is not taken from the ClientHealthMonitor.
Each client can have its own value.

> maximum-time-between-pings parameter in GatewayReceiver creation does not 
> have any effect
> -----------------------------------------------------------------------------------------
>
>                 Key: GEODE-8683
>                 URL: https://issues.apache.org/jira/browse/GEODE-8683
>             Project: Geode
>          Issue Type: Bug
>          Components: wan
>            Reporter: Alberto Gomez
>            Assignee: Alberto Gomez
>            Priority: Major
>              Labels: pull-request-available
>
> The maximum-time-between-pings parameter than can be set at gateway sender 
> creation has no effect, i.e. the value used as maximum time between pings for 
> gateway sender connections to the gateway receiver is either the default 
> value (60000) or the one set on the server where the receiver is running.
> The reason is that the ClientHealthMonitor is a server-side singleton that 
> monitors the health of all clients. The value set for this parameter in the 
> ClientHealthMonitor is first set when the server is started and the first 
> Acceptor is created.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to