Please fill out the form below before submitting, thank you!
[x] Bug exists Release Version 1.2.5 ( Master Branch)
[x] Bug exists in MQTTv3 Client on Snapshot Version 1.2.6-SNAPSHOT (Develop Branch)
[ ] Bug exists in MQTTv5 Client on Snapshot Version 1.2.6-SNAPSHOT (Develop Branch)
Currently, if there is a timeout for a MQTT, the client thread simply logs a message on level severe and afterwards throws a MqttEception (e.g. here). This exception type is "harder" to handle, as it is thrown on multiple occasions.
It would be nice if the client could provide callback options and only throw when the callback is not provided. Somewhat similar to e.g. the IMqttActionListener.
Please fill out the form below before submitting, thank you!
Currently, if there is a timeout for a MQTT, the client thread simply logs a message on level
severeand afterwards throws aMqttEception(e.g. here). This exception type is "harder" to handle, as it is thrown on multiple occasions. It would be nice if the client could provide callback options and only throw when the callback is not provided. Somewhat similar to e.g. theIMqttActionListener.