This repository has been archived by the owner on Jul 27, 2023. It is now read-only.
Fixes logging error in ConsulCache #60
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
If ConsulCache loses a connection to the agent then it will get an onFailure notification. That handler logs the error and then attempts to reconnect. However, the log line is malformed as a logger.error(...) cannot accept both string arguments and a throwable. This commit fixes that by putting the message + args in a String.format(...). This allows us to call LOGGER.error(String, Throwable).
rickfast
added a commit
that referenced
this pull request
Sep 6, 2015
Fixes logging error in ConsulCache
|
Thanks! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
If ConsulCache loses a connection to the agent then it will get an onFailure notification. That handler logs the error and then attempts to reconnect. However, the log line is malformed as a logger.error(...) cannot accept both string arguments and a throwable. This commit fixes that by putting the message + args in a String.format(...). This allows us to call LOGGER.error(String, Throwable).