Fix StatusLogger
time-zone issues and stack overflow
#2322
Merged
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.
This PR improves
StatusLogger
such thatlog4j2.StatusLogger.DateFormatZone
configuration property is introduced. This sets the time-zoneStatusLogger
uses to formatjava.time.Instant
. Without this formatting patterns accessing to time-zone-specific fields (e.g., year-of-era) cause failures. The value defaults toZoneId.systemDefault()
.StatusLogger
is improved to avoid stack overflow caused byStatusLogger#logMessage()
failures.These issues are originally reported by @lauredogit here: #2249 (comment)