|Re: [paho-dev] Paho C 1.3.0 reconnection issue|
The description of the issue in 604 is 'semaphore posted too many times'. This sounds like an inconvenience, but perhaps not a high priority issue. I think it's better to start with a description of the external effects, like that below ('reconnect can take up to 25 mins') rather than the internal behaviour, as then it's easier to prioritize.
One question I have is, does this happen if the connection is not using TLS?
On 05/03/2019 09:35, Milan Tucic wrote:
Hello community,Is there anyone who can try to reproduce issue with reconnection on Paho C 1.3.0? In case of a permanent connection, once it is lost, next successful connect will be postponed depending on number of signals sent to connect semaphore. In my case it was more then 50 connect retries. Depending on period, loss takes a lot of time (e.g. 50 x 30s = 25min).
The same can't be reproduced with Paho 1.2.0.
It is posted to project's github, but no word for more then one month. Link: https://github.com/eclipse/paho.mqtt.c/issues/604.
If there something more to clarify, just ask.
_______________________________________________ paho-dev mailing list paho-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/paho-dev-- Ian Craggs icraggs@xxxxxxxxxx IBM United Kingdom Eclipse Paho Project Lead & Mosquitto Committer
paho-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
Back to the top