IBM Support

PI92935: WAS 8.5 STOPSERVER SCRIPT INTERMITTENTLY RESULTS IN HANG, FAILS TO STOP SERVER.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • stopserver script intermittently fails to send signal to
    Websphere server to stop.  The JVM hangs due to waiting on
    class initialization lock
    
    Stack 1:
    3XMTHREADBLOCK     Waiting on:
    java/lang/J9VMInternals$ClassInitializationLock@0x00000000802AE8
    70 Owned
    by: <unowned>
    3XMHEAPALLOC             Heap bytes allocated since last GC
    cycle=0
    (0x0)
    3XMTHREADINFO3           Java callstack:
    4XESTACKTRACE                at
    com/ibm/ws/logging/WsLoggerFactoryImpl.createWsLogger(WsLoggerFa
    ctoryImp
    l.java:79)
    ...
    4XESTACKTRACE                at
    com/ibm/ws/bootstrap/WSLauncher.main(WSLauncher.java:280)
    
    Stack 2:
    3XMTHREADBLOCK     Waiting on:
    java/lang/J9VMInternals$ClassInitializationLock@0x0000000080152F
    10 Owned
    by: <unowned>
    3XMHEAPALLOC             Heap bytes allocated since last GC
    cycle=140312
    (0x22418)
    3XMTHREADINFO3           Java callstack:
    4XESTACKTRACE                at
    com/ibm/ws/logging/WsLoggerConfigurator.configureLogger(WsLogger
    Configur
    ator.java:459)
    4XESTACKTRACE                at
    com/ibm/ws/logging/WsLoggerFactoryImpl.createWsLogger(WsLoggerFa
    ctoryImp
    

Local fix

  • Use ENDJOB to end the Websphere server.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Run stopServer script intermittently    *
    *                      results in hang, fails to stop server.  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Deadlock may happen if any java class invoke JUL logging
    eariler than WebSphere application server logging framework
    initialization, no matter in start or stop process.
    

Problem conclusion

  • The problem was caused by different threads access the
    WsLogger class at the same time when the class is not
    initialized completely yet. The problem has been corrected.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.0.0.15, 8.5.5.14, and 9.0.0.8.  Please refer to the
    Recommended Updates page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI92935

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-01-25

  • Closed date

    2018-04-15

  • Last modified date

    2018-04-15

  • 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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R800 PSY

       UP

  • R850 PSY

       UP

  • R900 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
19 October 2021