fix: Set JVM console encoding to IBM-1047 for Java 21#4482
Merged
hrishikesh-nalawade merged 4 commits intov3.x.xfrom Feb 3, 2026
Merged
fix: Set JVM console encoding to IBM-1047 for Java 21#4482hrishikesh-nalawade merged 4 commits intov3.x.xfrom
hrishikesh-nalawade merged 4 commits intov3.x.xfrom
Conversation
Signed-off-by: hrishikesh-nalawade <hrishikesh.nalawade.17@gmail.com>
github-project-automation
bot
moved this to New
in API Mediation Layer Backlog Management
hrishikesh-nalawade
requested review from
achmelo,
pablocarle and
pavel-jares-bcm
and removed request for
achmelo and
pavel-jares-bcm
pablocarle
reviewed
Feb 3, 2026
Co-authored-by: Pablo Carle <pablocarle@users.noreply.github.com> Signed-off-by: Hrishikesh Nalawade <167364362+hrishikesh-nalawade@users.noreply.github.com>
…le-encoding' into hrishikesh-nalawade/GH4419/console-encoding
pablocarle
approved these changes
Feb 3, 2026
github-project-automation
bot
moved this from New
to Done
in API Mediation Layer Backlog Management
hrishikesh-nalawade
deleted the
hrishikesh-nalawade/GH4419/console-encoding
branch
Goutham024
pushed a commit
to Joe-Winchester/api-layer-OIDC-POC
that referenced
this pull request
Feb 4, 2026
Signed-off-by: hrishikesh-nalawade <hrishikesh.nalawade.17@gmail.com> Signed-off-by: Hrishikesh Nalawade <167364362+hrishikesh-nalawade@users.noreply.github.com> Co-authored-by: Pablo Carle <pablocarle@users.noreply.github.com> Signed-off-by: Gowtham Selvaraj <Gowtham.Selvaraj1@ibm.com>
Goutham024
pushed a commit
to Joe-Winchester/api-layer-OIDC-POC
that referenced
this pull request
Feb 4, 2026
Signed-off-by: hrishikesh-nalawade <hrishikesh.nalawade.17@gmail.com> Signed-off-by: Hrishikesh Nalawade <167364362+hrishikesh-nalawade@users.noreply.github.com> Co-authored-by: Pablo Carle <pablocarle@users.noreply.github.com> Signed-off-by: Gowtham Selvaraj <Gowtham.Selvaraj1@ibm.com>
Goutham024
pushed a commit
to Joe-Winchester/api-layer-OIDC-POC
that referenced
this pull request
Feb 4, 2026
Signed-off-by: hrishikesh-nalawade <hrishikesh.nalawade.17@gmail.com> Signed-off-by: Hrishikesh Nalawade <167364362+hrishikesh-nalawade@users.noreply.github.com> Co-authored-by: Pablo Carle <pablocarle@users.noreply.github.com> Signed-off-by: Gowtham Selvaraj <Gowtham.Selvaraj1@ibm.com>
1 task
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
2 participants
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
Java 21 (JEP 400) changed the default charset to UTF-8 for stdout/stderr. The z/OS SYSPRINT console expects EBCDIC (IBM-1047) encoding, causing UTF-8 bytes to display incorrectly. The existing
-Dlogging.charset.consoleproperty only configures Logback's encoder and takes effect after Spring Boot initialization, not at JVM startup.Added JVM-level properties for Java 21+ on z/OS:
-Dstdout.encoding=IBM-1047-Dstderr.encoding=IBM-1047These properties configure the JVM's
System.outandSystem.errstreams immediately at startup, before any application code runs, ensuring all console output uses the correct EBCDIC encoding.Linked to #4419
Checklist: