IV36700: STACKOVERFLOW ERROR WITH JAVA.UTIL.LOGGING

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • Error Message: java.lang.StackOverflowError happening soon after
    IBM JVM start.
    .
    Stack Trace: The repeating stack trace is
    at java.lang.J9VMInternals.newInstanceImpl(Native Method)
    at java.lang.Class.newInstance(Class.java:1355)
    at
    java.util.logging.LogManager.getInstanceByClass(LogManager.java:
    491)
    at java.util.logging.Logger.initHandler(Logger.java:448)
    at java.util.logging.Logger.getHandlers(Logger.java:481)
    at com.ibm.ejs.ras.Tr.logToWsHandlers(Tr.java:1717)
    at com.ibm.ejs.ras.Tr.systemErr(Tr.java:1000)
    at
    com.ibm.ejs.ras.SystemErrStream.dispatchEvent(SystemErrStream.ja
    va:282)
    at
    com.ibm.ejs.ras.SystemStream.doPrintLine(SystemStream.java:786)
    at com.ibm.ejs.ras.SystemStream.println(SystemStream.java:703)
    at
    com.ibm.ejs.ras.SystemErrStream.println(SystemErrStream.java:65)
    at java.util.logging.ErrorManager.error(ErrorManager.java:101)
    at
    java.util.logging.Handler.printInvalidPropMessage(Handler.java:1
    04)
    at java.util.logging.Handler.initProperties(Handler.java:151)
    at java.util.logging.StreamHandler.<init>(StreamHandler.java:65)
    at java.util.logging.FileHandler.<init>(FileHandler.java:169)
    .
    NA
    

Local fix

  • NA
    

Problem summary

  • The problem happens when there is an exception throw when
    initializing the log's handler, and then ErrorManager tries to
    print the error message to System.err, but System.err is
    redirected to a PrintStream owned by WAS which will initialize
    the log again, then it becomes an infinite recursion.
    

Problem conclusion

  • This defect will be fixed in:
    6.0.0 SR14
    6.0.1 SR6
    .
    The solution is to add a flag in Logger to mark it is already in
    initialization. When the flag is set, recursive initialization
    of handler is skipped and thus IBM JVM will not get into
    infinite recursion.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV36700

  • Reported component name

    JAVA CLASS LIBS

  • Reported component ID

    620700130

  • Reported release

    600

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-02-13

  • Closed date

    2013-03-18

  • Last modified date

    2013-03-18

  • 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

    JAVA CLASS LIBS

  • Fixed component ID

    620700130

Applicable component levels

  • R600 PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Runtimes for Java Technology
Java Class Libraries

Software version:

6.0

Reference #:

IV36700

Modified date:

2013-03-18

Translate my page

Machine Translation

Content navigation