Hi Dale,
There doesnt seem to be much more to try on the client side itself.
The only other thing you could do would be to use a modified local
copy of Proton to ignore the servers advertised 4 minute timeout value
and use something else for remoteIdleTimeout in its 'tick'
calculations to try and
Hi Robbie,
Thank you for your efforts!
I hardcoded this scheduling to be 30 sec. Then the behavior is as follows:
- the first empty packet is sent after 2.5 min;
- after that, the heartbeats are sent every 2 min.
However, this doesn't help, as the broker closes the connections (all but
the first
Hi Dale,
I tried to reproduce this on Friday using the existing idle-timeout
tests for the client and wasn't able to, the first heartbeat was sent
after 2 minutes, but upon a further look today I see why and tweaking
the test it now goes out after 4 and I can see what is going on.
The way the cli
Hi Robbie,
I was debugging a bit and saw that the broker behaves differently if there
is a single connection or multiple connections. That is, when I have only
one connection, it is not closed even after 5 minutes without heartbeats.
So, I'll try to observe the behavior with 2 or more connections
