tree 1c78b7b0e2686b8998572d92e7d2827349fa7beb
parent d1e003c822463e20ce43109e6dc3f6f72a110586
author Alberto Gomez <alberto.gomez@est.tech> 1604701858 +0100
committer GitHub <noreply@github.com> 1604701858 +1100
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJfpc6iCRBK7hj4Ov3rIwAAdHIIAAscBVLhuyEVst7ZynItM5Gj
 qhrKi0TJAroSC0tiPFb5q15tIo776t0gjyscon3PYMV7Rg4W9jkuFkClJXu/0NZa
 VYMg69DkLaxbWUwo1MgiFsDlr9NZTP2oxfs2YE3A4PElr6R86klvR/5+jMcOLQHn
 3rAC1Hc0NKFu7Pd85cPMYVfnsjEze9j5Pabdhro9uccLNJpQ6NuYdpFQxMb+wqGX
 c4k2jPKTQCbhsDJ7WUm6QX9PbXxgTkqm9334IcnCYbkAadvBNHYHgm+TDUcQxhk4
 Ehgimh0KT+4KmdS/RANLvSnT3mEBJgGDeb7ZRO8OflxVxD5B7C6HcP9HgTkGyVw=
 =Veak
 -----END PGP SIGNATURE-----
 

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.