VOOZH about

URL: https://www.ibm.com/support/pages/apar/IJ57789

⇱ IJ57789: ON Z/OS AND JZOS, THIRD-PARTY APPLICATIONS MAY PRODUCE GARBLED CHARACTERS IN LOGS AND CONSOLE OUTPUT.


IJ57789: ON Z/OS AND JZOS, THIRD-PARTY APPLICATIONS MAY PRODUCE GARBLED CHARACTERS IN LOGS AND CONSOLE OUTPUT.

APAR status

  • Closed as program error.

Error description

  • Error Message: None
    .
    Stack Trace:
    Applications exhibiting this symptom typically show stack traces
    that invoke ConsolePrintStream.write(..) APIs, where the data
    being written is encoded using the default (nonEBCDIC) charset.
    
    
    For example, the following stack trace from a Jenkins agent
    illustrates the issue:
    
    com.ibm.jvm.io.ConsolePrintStream.write
    (ConsolePrintStream.java:177)
    hudson.remoting.StandardOutputStream.write
    (StandardOutputStream.java:90)
    hudson.remoting.BinarySafeStream$2._write
    (BinarySafeStream.java:290)
    hudson.remoting.BinarySafeStream$2.write
    (BinarySafeStream.java:274)
    
    The resulting garbled output written to stdout or stderr may
    then be consumed by a parent process. This can lead to a hang or
    other incorrect behavior, often accompanied by stack traces that
    invoke ConsoleInputStream.read*() APIs.
    
    For example, the following stack trace from a Jenkins agent
    shows the corresponding read-side impact:
    
    java.io.FileInputStream.readBytes(byte[], int, int) (Native
    Method)
    java.io.FileInputStream.read(byte[], int, int)
    (FileInputStream.java:300)
    java.io.BufferedInputStream.fill (BufferedInputStream.java:291)
    java.io.BufferedInputStream.read1 (BufferedInputStream.java:347)
    
    java.io.BufferedInputStream.implRead
    (BufferedInputStream.java:420)
    java.io.BufferedInputStream.read (BufferedInputStream.java:399)
    com.ibm.jvm.io.ConsoleInputStream.read
    (ConsoleInputStream.java:275)
    .
    

Local fix

Problem summary

  • Applications such as Jenkins, Log4j, and Gradle that invoke
    System.out.write() or System.err.write() using the default
    charset may produce garbled characters in logs and console
    output. For Jenkins, we also observe a hang occurring when the
    Jenkins agent is running on a z/OS node.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IJ57789

  • Reported component name

    OPENJDK CLASS L

  • Reported component ID

    621800100

  • Reported release

    L00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2026-03-28

  • Closed date

    2026-03-31

  • Last modified date

    2026-03-31

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    OPENJDK CLASS L

  • Fixed component ID

    621800100

Applicable component levels

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSNVBF","label":"Runtimes for Java Technology"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"L00","Line of Business":{"code":"LOB08","label":"Cognitive Systems"}}]

Document Information

Modified date:
31 March 2026