-
Notifications
You must be signed in to change notification settings - Fork 4
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
"Packet identifiers do not match" #11
Comments
Thanks for the extended logs, this will help me track down this bug! I'll try to look at it ASAP. |
Any updates on this? |
Hi @siilike : I haven't been able to look at this yet, will do so ASAP. |
Here's the subscriber log:
|
Thanks!
That line is extremely strange, that should be an int and not some unicode characters. My best guess is that the internal counter for the message is off, this could have been introduced during the fix for #9. I'll try it out and let you know. You just ran the example file? Can you confirm that running https://github.com/unreal4u/mqtt/releases/tag/v1.1.0 this version everything is ok? (It will fail however if the message is over 127 bytes, but that is another issue). Greetings. |
Still same issue. I only changed MAXIMUM=10 in b4-publishMessageWithQoS2.php. It works when sleeping between messages, so the issue is how multiple messages are received. It's easy to test, just get ActiveMQ Artemis, run "bin/artemis create brokertest --user test --password test --allow-anonymous" to create a broker and then "brokertest/bin/artemis run". |
Ping. This is probably the best PHP MQTT library, but unusable when this bug is present. |
Hi, I have vacations now, so I'm finally able to take a look at this bug. Sorry for the delay but it's been quite busy lately. |
Hello, I was wondering about the status of this bug? I love this package, but at the moment it's consistently crashing for me. It's fairly easily reproducible too : if you change MAXIMUM from 1 to 10 in the publishMessageWithQoS2 example, and at the same time have the subscribeMultipleTopics running, you'll see it crash after about 1 or 2 messages, in fact, sometimes it fails to process any messages at all. So it definitely seems to struggle when processing > 1 messages. I'm not clever enough to attempt to fix it myself :) |
Hi @PFRene ! I haven't have made the time yet to fix this, but I have a pretty good idea of where the bug actually is and what I need to do to fix it. It is a not so obvious bug and pretty difficult to fix it in an appropriate manner. I will be working again soon on this library! Sorry and thanks for the patience! |
Your work is much appreciated - looking forward to future updates! |
Using latest master, ActiveMQ Artemis and MAXIMUM=10 in example b4:
The relevant identifiers are 1 and 57.
Artemis log:
The text was updated successfully, but these errors were encountered: