Setter for uncaughtExceptionHandler in ZBeacon Threads #299
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm making use of jeromq in a mobile application. The application uses
ZBeacon
for service discovery but being that its a mobile application a wifi connection cannot be gauranteed. If indeed the wifi connection drops jeromq's beacon threads will have an unhandled exception when they try to send/recv over the udp sockets.One way I have found to resolve this is to allow the application using the
ZBeacon
to set theThread.UncaughtExceptionHandler
s on each of the threads. Doing so lets the application catch that state and reset the beacon when wifi comes back.A working example here:
https://github.com/kevinkreiser/lapse_app/blob/master/app/src/main/java/kevinkreiser/lapse/ServiceNode.java#L150-L157