Made HystrixTimer initialization thread-safe #203
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hystrix-pull-requests #63 SUCCESS |
Closed
|
any chance this can be merged soon? we're seeing this frequently after the server starts |
benjchristensen
added a commit
that referenced
this pull request
Feb 7, 2014
Made HystrixTimer initialization thread-safe
|
Thank you @vadims About to release a maintenance release before the big changes of 1.4. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The current initialization in
HystrixTimeris not thread-safe: one thread may create theScheduledExecutor, but a second thread may try to use it before it has been initialized, resulting in aNullPointerException. This race is easy to replicate by starting multiple Threads that each run a HystrixCommand simultaneously.This pull fixes this by looping on the appropriate initialization condition.