My query is: If that issue was really fixed, then in which docker image is that fix available, so I could pull and deploy the same MQTT 3 docker image to resolve the aforementioned errors? Quick support on this issue would be very much appreciated, thanks in advance.
The issue has been successfully addressed in the hivemq-mqtt-client, and you can find the details of the fix in the ticket as you can see in the provided image:
Hi @Daria_H yes, I stand corrected, this issue was in HiveMQ MQTT client and not in broker.
However, this issue was apparently fixed in the 1.2 version of hivemq-mqtt client and I am using 1.3.2 version of hivemq-mqtt client, in which this fix should be there as it’s a later version than 1.2.
I appreciate your diligence in identifying the source of the issue in the HiveMQ MQTT client and providing information about the versions.
To assist you further, could you please share the steps you took to reproduce the issue? If the reproduction involves a specific bash command or a Java project, kindly provide the details or, in the case of a Java project, share the link to the repository or upload it to a file share. This information will be invaluable for our investigation.
Additionally, to better understand the context, could you let us know which MQTT 3 broker you are using? Knowing the broker version can help us delve deeper into the problem and expedite the resolution process.
Your cooperation in providing these details will significantly aid us in making progress toward a resolution.
