IBM Support

PI06129: SERVER FAILS TO START WHEN JDK SWITCHED FROM 1.7 TO 1.6

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Server fails to start when jdk switched from Java 7 to Java 6.
    
    After a nodeagent or profile is switched to Java 7, and a
    server managed by that agent or within that profile is switched
    to Java 6, that server might not start.
    
    The following error is seen in native_stdout log file:
    Error occurred during initialization of VM
    java.lang.UnsupportedClassVersionError:
    java/security/cert/Certificate
    : Unsupported major.minor version 51.0
    at java.lang.Class.getDeclaredMethods0(Native Method)
    at
    java.lang.Class.privateGetDeclaredMethods(Class.java:2436)
    at java.lang.Class.getDeclaredMethod(Class.java:1937)
    at
    java.security.SecureClassLoader.<clinit>(SecureClassLoader.java:
    45)
    at sun.misc.Launcher.<init>(Launcher.java:55)
    at sun.misc.Launcher.<clinit>(Launcher.java:43)
    at
    java.lang.ClassLoader.initSystemClassLoader(ClassLoader.java:133
    7)
    at
    java.lang.ClassLoader.getSystemClassLoader(ClassLoader.java:1319
    )
    

Local fix

  • Change nodeagent and appserevr to use jdk 1.6 (jdk for
    nodeagent being at higher level is causing problems)
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server running mixed versions of JDK        *
    ****************************************************************
    * PROBLEM DESCRIPTION: After switching an appserver from       *
    *                      Java 1.7 to 1.6, it will not start if   *
    *                      the node agent or profile default       *
    *                      remains at Java  1.7.                   *
    ****************************************************************
    * RECOMMENDATION:  Install a fix pack containing this APAR     *
    ****************************************************************
    When a launching process running Java 1.7 starts a server
    process running Java 1.6, the endorsed library path of the
    launched 1.6  process can contain libraries for 1.7, which can
    cause a startup failure.
    

Problem conclusion

  • The process launcher code is revised to not pass endorsed
    directories from the launcher process to the launched process
    for the affected platforms.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.5.5.3.  Please refer to the Recommended Updates
    page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

  • Use startServer.sh with the -script option to generate a
    startup script, then edit that script to remove endorsed
    directory paths that point to Java 1.7 libraries.
    

Comments

APAR Information

  • APAR number

    PI06129

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-11-13

  • Closed date

    2014-01-24

  • Last modified date

    2014-01-24

  • 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

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022