[
https://issues.apache.org/jira/browse/GEODE-8683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alberto Gomez updated GEODE-8683:
---------------------------------
Description:
The maximum-time-between-pings parameter than can be set at gateway receiver
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.
was:
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.
> 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
> Fix For: 1.14.0
>
>
> The maximum-time-between-pings parameter than can be set at gateway receiver
> 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)
