IBM Support

PM39993: EXCESS MEMORY UTILIZATION ON THREADLOCAL IN XMLTYPEUTIL CAN CAUSE SERVANT REGION TO ABEND.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The Eclipse class
    "org.eclipse.emf.ecore.xml.type.util.XMLTypeUtil"
    will see excess memory utilization in a thread local variable
    when XML data containing large character data sections is parsed
    This can lead to threads timing out due to heavy GC to clean up
    the heap consumed by these large ThreadLocal objects, and
    eventually cause Servants to abend with an EC3.
    

Local fix

  • na
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Excess memory utilization will occur    *
    *                      on thread local  variable               *
    *                      org.eclipse.emf.ecore.xml.type.util.XML *
    *                      TypeUtil$CharArrayThreadLocal when      *
    *                      XML data containing large character     *
    *                      data sections (CDATA sections) is       *
    *                      parsed.  This can lead to threads       *
    *                      timing out due to heavy garbage         *
    *                      collection (GC) and eventually cause    *
    *                      Servants to abend with an EC3.          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The problem occurs because the thread local variable
    org.eclipse.emf.ecore.xml.type.util.XMLTypeUtil$CharArrayThreadL
    ocal performs an allocation which is proportional to the size
    of the character data sections (CDATA sections) which are
    processed.  Because of how threads are managed, that leads to
    an effective permanent static allocation.
    

Problem conclusion

  • The problem was resolved by rewriting XMLTypeUtil to remove
    unnecessary allocations, including the removal of the thread
    local variable which caused the excess memory allocation.
    
    APAR PM39993 is currently targeted for inclusion in
    Service Level (Fix Pack) 7.0.0.19 of WebSphere
    Application Server.
    
    Please refer to URL:
    //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
    for Fix Pack availability.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM39993

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2011-05-24

  • Closed date

    2011-06-23

  • Last modified date

    2017-06-22

  • APAR is sysrouted FROM one or more of the following:

    PM34450

  • APAR is sysrouted TO one or more of the following:

    106PC1Ÿ

Fix information

  • Fixed component name

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R700 PSY UK71297

       UP11/09/10 P F109

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
10 February 2022