-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
on connection callback not triggered on reconnection to the same broker with the same mosq instance #2974
Comments
Please try to look at the PR #2966 .. it may be the same problem. |
I don't think it's the same, but I'll give your branch a go anyway. |
Should a new connection be made with a fresh |
Using |
mosquitto version: 2.0.18
system: ubuntu, kernel 5.15.0-91
Hi,
I've noticed that when running
mosquitto_connect
ormosquitto_connect_async
on mosquitto instance that has just been disconnected from a broker, the connection callback is not triggered, even if the broker (the same broker) actually receives a connection request and reponds with a CONNACK message. This results in logs that look like below:The timeout happens because there connection callback is never triggered.
Is this the expected behavior? If yes, then it would mean that after a disconnect the mosquitto instance has to be always destroyed or reinitialized, is that the right way?
The text was updated successfully, but these errors were encountered: