You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @raddatzk - thanks for the bug report and great supplementary repo with code!
There should be some protections against breaking the entire event stream although if end user consumer code is throwing exceptions, should that be hidden? Logged?
The best case is if consumer code protects against this as your work-around.
I'll need to give this some thought but in the meantime, this is a good note for other users. Consumer code should be careful to not let unexpected exceptions percolate up.
We've filed a feature request in #624 to improve exception handling in the client. I'll close out this issue but if you have any other input/feedback, let us know!
Expected behavior
After an exception occurred while consuming an mqtt 3 event, mqtt should continue consuming events
Actual behavior
A reactivex UndeliverableException will be thrown and no more events will be consumed
To Reproduce
Checkout the example repository and follow the steps from the README
Details
The text was updated successfully, but these errors were encountered: