On 10/12/2020 22:30, Gordon Sim wrote:
On 10/12/2020 16:04, Toralf Lund wrote:
Where and when exactly are the heartbeats sent?
The interval is negotiated at connection time. I believe the default
for the 0-10 qpid::messaging client is 0, i.e. heartbeats disabled, so
I suspect your client has some configuration setting a non-zero value?
Yes. It connects with option "heartbeat". I've been experimenting with
different values, but 5 is currently used.
Heartbeats only need to be sent if there has been no other traffic in
that negotiated interval. The client or server will consider the
connection failed if nothing arrives for twice the interval.
That's useful info. I was under the impression that heartbearts would
always be sent, and that the system might dumbly consider only those
when deciding if the connection was good or not.
My software gets data from a bunch of other systems that might
theoretically all be switched off or have their data disabled in some
other manner, but it a more normal situation, heartbeats should actually
never be necessary.
What might cause problems to occur?
The only issues I have ever seen have been either genuine networking
issues or cpu starvation (on extremely heavily loaded server).
I'm at a loss to explain what you are seeing I'm afraid.
Right... I guess I'll just have to keep trying various changes etc.
Although I'm a bit out of ideas just now.
- Toralf
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
