This repository has been archived by the owner on Aug 7, 2023. It is now read-only.
UberHandler heartbeat timeout being reset on send OR receive #219
Comments
nicktindall
changed the title
HearbeatHandler timeout being reset on send OR receive
UberHandler heartbeat timeout being reset on send OR receive
Oct 27, 2022
nicktindall
added a commit
to OpenHFT/OpenHFT
that referenced
this issue
Oct 28, 2022
Released in Chronicle-Network-2.24ea2, BOM-2.24ea6 |
Released in Chronicle-Network-2.23.23, BOM-2.23.131 |
Released in Chronicle-Network-2.22.16, BOM-2.22.165 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The timeout in the UberHandler's HeartbeatHandler is being reset on every send OR receive. So it effectively never triggers. As long as you're sending heartbeats, it won't time-out, even if it's not receiving any from the other side:
Chronicle-Network/src/main/java/net/openhft/chronicle/network/cluster/handlers/UberHandler.java
Lines 289 to 293 in 7d76645
The text was updated successfully, but these errors were encountered: