Hello, first of all thank you for your work, as it is a very well done client, and with very good features.
I just wanted to comment something that we are detecting, especially with corporate brokers like ActiveMQ or RedHat AMQ...
It seems that even if we do not have the check marked as retain, for the broker, all messages from the client mqtt-explorer, are marked as retain.
On the other hand, in a broker with a high workload, the deletion option, as soon as the mqtt-explorer has been open for a couple of minutes, does not work, since the volume of messages that arrive to it, makes the deletion ineffective.
(We have tested version 0.3.5 and beta 0.40-b1, in several operating systems and with the same problem.
We believe that it would be great to implement some added configuration, on the side of mqtt-explorer, for this type of operation, where you don't want neither retained msg and msg in queue.
Is it possible, that someone has experienced this before? is there any possible solution?
Thank you!
Hello, first of all thank you for your work, as it is a very well done client, and with very good features.
I just wanted to comment something that we are detecting, especially with corporate brokers like ActiveMQ or RedHat AMQ...
It seems that even if we do not have the check marked as retain, for the broker, all messages from the client mqtt-explorer, are marked as retain.
On the other hand, in a broker with a high workload, the deletion option, as soon as the mqtt-explorer has been open for a couple of minutes, does not work, since the volume of messages that arrive to it, makes the deletion ineffective.
(We have tested version 0.3.5 and beta 0.40-b1, in several operating systems and with the same problem.
We believe that it would be great to implement some added configuration, on the side of mqtt-explorer, for this type of operation, where you don't want neither retained msg and msg in queue.
Is it possible, that someone has experienced this before? is there any possible solution? Thank you!