IBM Support

IJ18484: EXCEPTIONININITIALIZERERROR WHEN JAVAX.MANAGEMENT.BUILDER.INITIAL CLASS NOT FOUND

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Error Message: ExceptionInInitializerError when
    javax.management.builder.initial class not found
    .
    Stack Trace: Exception in thread "main"
    java.lang.ExceptionInInitializerError
            at
    java.lang.J9VMInternals.ensureError(J9VMInternals.java:148)
            at
    java.lang.J9VMInternals.recordInitializationFailure(J9VMInternal
    s.java:137)
            at
    java.lang.management.ManagementFactory.getPlatformMBeanServer(Ma
    nagementFactory.java:247)
            ...
    Caused by: javax.management.JMRuntimeException: Failed to load
    MBeanServerBuilder class NonExistentClass:
    java.lang.ClassNotFoundException: NonExistentClass
            at
    javax.management.MBeanServerFactory.checkMBeanServerBuilder(MBea
    nServerFactory.java:503)
            at
    javax.management.MBeanServerFactory.getNewMBeanServerBuilder(MBe
    anServerFactory.java:539)
            at
    javax.management.MBeanServerFactory.newMBeanServer(MBeanServerFa
    ctory.java:316)
            at
    javax.management.MBeanServerFactory.createMBeanServer(MBeanServe
    rFactory.java:231)
            at
    javax.management.MBeanServerFactory.createMBeanServer(MBeanServe
    rFactory.java:192)
            at
    java.lang.management.ManagementFactory$ServerHolder.<clinit>(Man
    agementFactory.java:466)
            ...
    .
    

Local fix

Problem summary

  • When the class specified in the javax.management.builder.initial
    system property cannot be found, the JMX MBean server fails to
    start. Before Java 8.0.5.0, and in other Java implementations,
    when the javax.management.builder.initial class is not found,
    then a javax.management.JMRuntimeException is thrown, which can
    be caught and handled gracefully. The issue fixed here is that
    after Java 8.0.5.0, the IBM SDK for Java throws an
    ExceptionInInitializerError, which is not handled in the same
    way, causing an application error.
    

Problem conclusion

  • The Java SDK has been updated to throw an exception that can be
    handled as before, rather than an ExceptionInInitializerError.
    .
    This APAR will be fixed in the following Java Releases:
       8    SR5 FP41  (8.0.5.41)
    .
    Contact your IBM Product's Service Team for these Service
    Refreshes and Fix Packs.
    For those running stand-alone, information about the available
    Service Refreshes and Fix Packs can be found at:
               https://www.ibm.com/developerworks/java/jdk/
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ18484

  • Reported component name

    J9 COMMON CODE

  • Reported component ID

    620700127

  • Reported release

    270

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-08-21

  • Closed date

    2019-08-21

  • Last modified date

    2019-09-10

  • 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

    J9 COMMON CODE

  • Fixed component ID

    620700127

Applicable component levels

  • R270 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSNVBF","label":"Runtimes for Java Technology"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
21 February 2022