A rough guide from memory so it might not be 100%:
For sender/receiver pair, the heartbeat is the longest period of time the sender will do nothing before it sends a dummy packet to ensure the connection is still alive (the send may fail if the socket/conn has dropped or on the receive of the response). Similarly the receiver waits on a receive with a timeout which is a formula based off the heartbeat value. Therefore the receiver should always be woken with either a heartbeat or a message and if it times out, then it drops the connection. Note the receiver will also send a heartbeat back to the sender as a response to a heartbeat being received.
For client connections, IF a client app is inside an MQGET then it behaves as above, ie sending periodic heartbeats to ensure the connection stays alive. Outside an MQGET the heartbeat does nothing
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum