-
Notifications
You must be signed in to change notification settings - Fork 33
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
QoS 1/2 doesn't work #2
Comments
@Amblego , was QoS 1/2 working for you before my last commit? |
@sskaje, before your last commit in my case (start_sub_with_client_id + subscribe + kill_without_unsubscribe, start_pub + publish, start_sub_with_the_same_client_id_as_before + subscribe - as described above) script fallen down on second subscription stage.. |
@Amblego did you try to use mosquitto_pub/mosquitto_sub? how are these two performing like? |
@sskaje , in console utils everything is OK: brabantia@debian: |
And in debug mode: brabantia@debian: |
I tried
in subscriber, something is wrong. |
@Amblego code:
subscribe.php
Can you try if this works you there? |
@sskaje, |
Sskaje, thank you for quick actions!
Problem with uncaught exception was fixed, but it seems QoS 1/2 doesn't work.
For example: I start the subscribe script, after subscribe (with QoS=1 or 2) action I kill the script. After that I run publish script - it send some messages with QoS=1 or 2 and I kill it.
After that I run the same subscribe script (with QoS=1 or 2 and the same client_id) and there are no messages...
Where is my mistake?
The text was updated successfully, but these errors were encountered: