IBM Support

PI29073: OUT OF MEMORY ERROR USING COM.IBM.XLTXE.MM1MFCG.BEL.FCGMETHODGENBCEL

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The com.ibm.xltxe.mm1mfcg.bel.FcgMethodGenBCEL object occupies
    a large amount of heap.
    
    This happens when there are many match statements in the
    stylesheet that apply to the templates method that get
    generated, this can exceed the Java method size limit when
    using the compileXSLT method from XCompilationFactory in order
    to pass in compilation parameters (XCompilationParameters).
    The 'compileXSLT' method always uses the compiler, since only
    the compiler can generate bytecodes/classes. The 'prepareXSLT'
    method will return an executable that could be cached and
    re-used and whether interpreter or compiler is to be used to
    create the executable can be controlled by XStaticContext's
    setUseCompiler method.
    

Local fix

  • Customers can use the interpreter by not setting the use
    compiler setting or setting it to false:
    XStaticContext sc = factory.newStaticContext();
    sc.setUseCompiler(false);
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Out of memory error when compiling a    *
    *                      stylesheet with many match statements.  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    An out of memory error can occur when compiling a stylesheet
    that contains many match statements using either the
    XCompilationFactory or XFactory.prepareXSLT where the
    XStaticContext passed in has setUseCompiler set to true.  If
    setUseCompiler is false (the default) then the interpreter is
    used and this problem does not occur.
    

Problem conclusion

  • The problem is fixed under a new system property.  To enable
    the fix set the
    com.ibm.xltxe.rnm1.xtq.processor.alternateApplyTemplatesHandling
     system property to true, for example:
    -Dcom.ibm.xltxe.rnm1.xtq.processor.alternateApplyTemplatesHandli
    ng=true.  The fix may have a minor effect on the performance
    of the compiled stylesheet so only use when necessary.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 8.0.0.10 and 8.5.5.5.  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

    PI29073

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-11-05

  • Closed date

    2014-12-15

  • Last modified date

    2015-02-10

  • 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

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R800 PSY

       UP

  • R850 PSY

       UP

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

Document Information

Modified date:
27 April 2022