IBM Support

PH08828: OUTOFMEMORY IN INJECTIONENGINE CACHE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Liberty (CICS) runs into out-of-memory condition at
    com.ibm.ws.injectionengine.osgi.internal.OSGiReferenceContex
    tImp
    lwhich is comparable to PI66621. yet we deal with another
    cache
    of the injection engine
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of IBM WebSphere Application Server   *
    *                  Traditional or Liberty with Dynamic JSP     *
    *                  classes being processed by the              *
    *                  InjectionEngine                             *
    ****************************************************************
    * PROBLEM DESCRIPTION: OutOfMemory Error coming from           *
    *                      InjectionEngine for                     *
    *                      OSGiReferenceContextImpl                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Users can hit an OutOfMemory (OOM) error when using Dynamic
    JSP
    classes that are regenerated. Memory analysis will point to
    "com.ibm.ws.injectionengine.osgi.internal.OSGiReferenceConte
    xtIm
    pl"  loaded by "com.ibm.ws.injection" occupying a high
    amount of
    memory for ivProcessedInjectionClasses in
    com.ibm.ws.injection.core/src/com/ibm/ws/injectionengine/Ref
    eren
    ceContextImpl.java
    This is caused by the InjectionEngine storing a cache of
    processed classes, since dynamic JSP classes can constantly
    regenerate, they will continue to grow the cache.
    

Problem conclusion

  • Injection Engine will be updated to cap the size of the
    Processed classes in the case when we are dynamically
    processing
    injection targets. We do not cap the processed classes cache
    during regular processing done at server startup.
    
    The fix for this APAR is currently targeted for inclusion in
    fix
    pack 19.0.0.3 for Liberty, 9.0.5.0 and 8.5.5.16 for
    WebSphere
    Application Server.  Please refer to the
    Recommended
    Updates page for delivery information:
    http://www.ibm.com/support/docview.wss?
    rs=180&uid=swg27004980
    

Temporary fix

  • Only workaround is a server restart to clear out the cache.
    

Comments

APAR Information

  • APAR number

    PH08828

  • Reported component name

    LIBERTY PROF -

  • Reported component ID

    5655W6514

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-02-21

  • Closed date

    2019-04-02

  • Last modified date

    2019-04-04

  • 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

    LIBERTY PROF -

  • Fixed component ID

    5655W6514

Applicable component levels

  • R850 PSY

       UP

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

Document Information

Modified date:
28 April 2022