Propagate all exceptions that occur in connectTimeout thread #9
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 experience an issue on production for maxwell, where an exception occurred during connection to a database that had experienced many failovers. However the exception was uncaught, and our maxwell container continued to operate in a bad state.
Going through the code here, it looks like only IOExceptions were caught by the code, causing the IllegalStateException thrown when there is already a connection to fall through the cracks. Here we force all exceptions to propagate out, and successfully terminate the application when one occurs.