Add charset in logger based on Z/Os#2398
Draft
Sparsh Gupta (sp-gupta) wants to merge 1 commit into
Draft
Conversation
bd98a42 to
915daa7
Compare
This file contains hidden or 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
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.
Description
In INC-8143, customer is seeing unreadable logs in the z/os system as the logs are not translated to EBCDIC format.
Default charset in Java 21 is defined by JDK (defaulting to UTF-8).
In Java 8, it is defined by the OS (thus defaulting to IBM-1047 for Z/Os) and that's why previous CP versions didn't face this issue.
Added a config which appends the appropriate charset in the log4j2 configuration.
Type of change
How Has This Been Tested?
Z/os pipeline is broken with CP Test Env. We currently don't have a way to test this out.
Checklist: