You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'll add some clarification, I was using TCP in my case. So I'm pretty sure this is a bug as opposed to a feature request.
Nevermind the RADIO and DISH sockets both use the udp_engine implementation, which does not yet support heatbeating, like bluca said.
jean-airoldie
changed the title
Problem: Hearbeating with RADIO/DISH always times out
Problem: TCP Hearbeating with RADIO/DISH always times out
Jun 23, 2019
jean-airoldie
changed the title
Problem: TCP Hearbeating with RADIO/DISH always times out
Problem: Hearbeating not supported by RADIO/DISH
Jun 24, 2019
sigiesec
changed the title
Problem: Hearbeating not supported by RADIO/DISH
Problem: Heartbeating not supported by RADIO/DISH
Oct 15, 2019
Related to #3550
Issue description
Setting a ZMQ_HEARTBEAT_IVL to either (or both) DISH or RADIO eventually causes the DISH socket to no longuer receive messages over TCP.
Environment
Minimal test code / Steps to reproduce the issue
What's the actual result? (include assertion message & call stack if applicable)
The DISH socket will receive messages for a while, but eventually all
recv
callswill return
EAGAIN
.What's the expected result?
The DISH socket should always receive the messages coming from the RADIO socket.
The text was updated successfully, but these errors were encountered: