IBM Support

PH39981: JVM MBEAN DUMPTHREADS() CAN CREATE HEAP OR SYSTEM CORE DUMPS

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

  • On non-Windows platforms, if Java dump handlers are configured t
    trigger heap and/or core dumps on user dump events, the JVM
    MBean's dumpThreads() method will create these dumps in addition
    to the requested thread dump
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: The dumpThreads() method of the WAS JVM *
    *                      MBean can trigger other dump handlers   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The WAS JVM MBean provides a dumpThreads() method that's
    intended
    to create a thread dump of the JVM. However, due to the way that
    this method is currently implemented on non-Windows platforms,
    it
    will trigger all dump handlers that are configured on user dump
    events. This can be a problem if more heavyweight dumps (such as
    heap or system core dumps) are configured for these events, as
    there is no way to effectively get thread dumps alone.
    

Problem conclusion

  • The JVMMBean.dumpThreads() was modified to utilize the IBM J9
    JVM's JavaDump class to create a javacore (the intended output
    of a thread dump request) on supported platforms. Non-IBM JVM
    platforms (Solaris and HP-UX) will retain the legacy behavior,
    triggering thread dumps by signaling the process.
    
    The fix for this APAR is targeted for inclusion in fix packs
    9.0.5.13 and 8.5.5.22. For more information, see 'Recommended
    Updates for WebSphere Application Server':
    https://www.ibm.com/support/pages/node/715553
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH39981

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-08-20

  • Closed date

    2022-06-20

  • Last modified date

    2022-06-20

  • 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

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

Document Information

Modified date:
21 June 2022