IBM Support

PM33638: SCA CLASSLOADERS RETAINED IN MEMORY AFTER BLA STOP

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Product Release and Version Information: WebSphere Application
    Server Base Version 7.0 with Feature Pack for Service Component
    Architecture (SCA) V1.0.1.
    
    Problem Desciption:
    
    SCA Classloaders retained in memory after business-level
    application (BLA) stop
    

Local fix

  • Local Fix/Work Around: None
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All IBM WebSphere Application Server 7.0    *
    *                  Feature Pack for Service Component          *
    *                  Architecture (SCA) users.                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: After Business Level Application (BLA)  *
    *                      stop, SCA class loaders are retained    *
    *                      in memory, potentially leading to       *
    *                      OutOfMemoryExceptions when restarting   *
    *                      SCA applications.                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    After a BLA stops, we expect all SCA class loaders
    associated with the application to be available for garbage
    collection. However, analysis of a heap dump showed
    multiple SCA class loaders with the same pattern of class
    loading were retained in memory after restarting the BLA a few
    times.
    
    Analysis of the heap dump showed the following classes were
    retaining references to the SCA class loaders, preventing the
    class loaders from being garbage collected:
    
    1)com.ibm.ws.soa.sca.databinding.sdo.SCAManagedHelperContext
    2)org.apache.tuscany.sca.databinding.sdo.schemaresolver.SCAFEPCl
    assloaderAggregatedSchemaResolver
    3)com.ibm.ws.soa.sca.admin.runtime.impl.SCAClassLoader
    4)com.ibm.ws.naming.jcache.CacheKey - JNDI lookups are cached
    by WebSphere naming code using the application class loader as
    the key. See APAR PM33867.
    

Problem conclusion

  • The Feature Pack for Service Component Architecture (SCA) was
    updated so references to the SCA class loader are removed
    during BLA stop. To address references being held by
    com.ibm.ws.naming.jcache.CacheKey APAR PM33867 must also be
    applied to the system.
    
    The fix for APAR PM33638 is currently targeted for inclusion in
    fix pack 1.0.1.11. 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

    PM33638

  • Reported component name

    WAS SCA FEATURE

  • Reported component ID

    5724J0854

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-02-25

  • Closed date

    2011-03-07

  • Last modified date

    2011-03-07

  • 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

    WAS SCA FEATURE

  • Fixed component ID

    5724J0854

Applicable component levels

  • R700 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SUPPORT","label":"IBM Worldwide Support"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"1.0.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
09 February 2022