OK, thank you for the feedback Roger. The next time we update I may test the original order again out of curiosity, but since the order really doesn’t seem to make any difference,
I’ll likely just leave it as it is now.
Thanks.
From: Roger Light <roger@xxxxxxxxxx>
Sent: Tuesday, May 2, 2023 9:36 AM
To: General development discussions for the mosquitto project <mosquitto-dev@xxxxxxxxxxx>
Cc: Maynard, Chris <Christopher.Maynard@xxxxxxx>
Subject: Re: [mosquitto-dev] mosquitto_connect_bind_async() and mosquitto_loop_start() order of usage
It should work either way, as you say, but there have been bugs around this in the past. Since at least 2.0 there have been tests that cover both cases, so I'm confident if you upgrade to that it should work as expected.
We had been using mosquitto 1.4.14 but recently updated to 1.6.8 and discovered that our client could no longer connect to the broker.
The documentation for
mosquitto_connect_bind_async() indicates that, “May be called before or after
mosquitto_loop_start.”
Well, we had been calling it *before* mosquitto_loop_start(). Once I swapped the order and called it *after*
mosquitto_loop_start(), our client could once again successfully connect.
Has anyone run into this before? Is this a known problem? I couldn’t find any open issue for this.
CONFIDENTIALITY NOTICE: This message is the property of International Game Technology PLC and/or its subsidiaries and may contain proprietary, confidential or trade secret information. This message is intended solely for the use of the addressee. If you are
not the intended recipient and have received this message in error, please delete this message from your system. Any unauthorized reading, distribution, copying, or other use of this message or its attachments is strictly prohibited.
|