IBM Support

PH13915: HIGH CPU WHEN SYNCHRONIZING RESOURCES.XML

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

  • When synchronizing the resources.xml high CPU usage is seen. One
    thread is consuming most of the CPU. In javacore we can see the
    following:
    
    "Non-deferrable Alarm : 3" J9VMThread:0x000000008401D200,
    j9thread_t:0x00007F34A401A008,
    java/lang/Thread:0x0000000004728E18, state:R, prio=5
    CPU usage total: 573.084799690 secs
    Heap bytes allocated since last GC cycle=41278128 (0x275DAB0)
    Java callstack:
    at java/util/TimSort.mergeHi(TimSort.java:870(Compiled Code))
    at java/util/TimSort.mergeAt(TimSort.java:501(Compiled Code))
    at
    java/util/TimSort.mergeForceCollapse(TimSort.java:442(Compiled
    Code))
    at java/util/TimSort.sort(TimSort.java:239(Compiled Code))
    at java/util/TimSort.sort(TimSort.java:189(Compiled Code))
    at java/util/Arrays.sort(Arrays.java:867(Compiled Code))
    at
    com/ibm/ws/runtime/config/ConfigDocumentImpl.load(ConfigDocument
    Impl.java:212(Compiled Code))
    (entered lock:
    com/ibm/ws/runtime/config/ConfigDocumentImpl@0x000000006AB41EF8,
    entry count: 1)
    at
    com/ibm/ws/runtime/config/ConfigServiceImpl.getDocument(ConfigSe
    rviceImpl.java:182(Compiled Code))
    at
    com/ibm/ws/runtime/config/ConfigServiceImpl.getDocumentObjects(C
    onfigServiceImpl.java:126(Compiled Code))
    at
    com/ibm/ws/runtime/config/ConfigServiceImpl.getDocumentObjects(C
    onfigServiceImpl.java:120(Compiled Code))
    at
    com/ibm/ejs/j2c/mbeans/DataSourceMbeanImpl.configChanged(DataSou
    rceMbeanImpl.java:581(Compiled Code))
    at
    com/ibm/ws/management/component/ConfigChangeHandler$ConfigChange
    EventDispatcher.run(ConfigChangeHandler.java:369)
    at
    com/ibm/ws/management/component/ConfigChangeHandler.alarm(Config
    ChangeHandler.java:171)
    at com/ibm/ejs/util/am/_Alarm.runImpl(_Alarm.java:151(Compiled
    Code))
    at com/ibm/ejs/util/am/_Alarm.run(_Alarm.java:136(Compiled
    Code))
    at com/ibm/ws/util/ThreadPool$Worker.run(ThreadPool.java:1892)
    
    This thread is not hung, so looking from one javacore to another
    we see it progress.
    

Local fix

  • Not available.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server using a large number of datasources  *
    *                  with one server.                            *
    ****************************************************************
    * PROBLEM DESCRIPTION: High CPU may occur when many            *
    *                      datasources are configured in the       *
    *                      same server.                            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When processing the large number of datasource in the
    resources.xml file, customer may see this in the stack
    com/ibm/ws/runtime/config/ConfigServiceImpl.getDocumentObjects(C
    onfigServiceImpl.java:126(Compiled Code))
    at
    com/ibm/ws/runtime/config/ConfigServiceImpl.getDocumentObjects(C
    onfigServiceImpl.java:120(Compiled Code))
    at
    com/ibm/ejs/j2c/mbeans/DataSourceMbeanImpl.configChanged(DataSou
    rceMbeanImpl.java:581(Compiled Code))
    which is processing datasource.  When there are 500 or more
    datasource, this procession can cause high CPU usage.
    

Problem conclusion

  • Code was added to avoid the processing of datasources during
    server startup unless the processing is required.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.5.5.17 and 9.0.5.1.  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

    PH13915

  • 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

    2019-06-28

  • Closed date

    2019-09-09

  • Last modified date

    2019-09-09

  • 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



Document information

More support for: WebSphere Application Server
General

Software version: 850

Reference #: PH13915

Modified date: 09 September 2019