-
Notifications
You must be signed in to change notification settings - Fork 153
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
No support of providing exceptions while using Mqtt5AsyncClient #566
Comments
Line 93 in d709dc3
|
Thanks for reaching out. At a first glance, it looks like the async programming might not be correct. You might not synchronize threads within your application. For example, this connect method has a blocking signature (e.g. no return future) but not blocking for the connect operation of the client. So most likely this is where the issue happens. And there might be two options:
|
The I would like to share with you the background of it. I wanted to introduce a new callback to understand about a situation when the OSGi messaging adapter (the source code link you already have) encounters issues to connect to the broker due to issues like invalid password, broker unreachable, protocol error etc. That's why, I wanted to introduce a new API for other consumers to implement. For this, I wanted to handle the exceptional information which is passed to the That's why, I open this issue. FYI I found a better way to implement the aforementioned functionality by implementing But, I still cannot get the |
Currently, the
Mqtt5AsyncClient
doesn't propagate the exceptions that might have been caused while connecting to the broker, for example, due to unreachable broker, wrong password etc.The RX Client callback
doOnError
or theCompletableFuture
callbackexceptionally(..)
is never executed in such scenarios.The text was updated successfully, but these errors were encountered: