IBM Support

IT36793: PERFORMANCE ISSUE WITH XSLTRANSFORM NODE IF THE STYLE SHEETS ARE PLACED ON AN NFS SHARED FILE SYSTEM.

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

  • XSLTransform provide has property stylesheet cache level to
    specify the stylesheets to be compiled and cached. But even if
    the stylesheet is in the cache, during the processing of each
    input message the stylesheet file is accessed from the file
    system. This is to check the last modified time of the
    stylesheet and to determine whether the cache contains the
    correct version of the stylesheet. But accessing the stylesheet
    from the file system for each input message can cause a
    performance issue if the file operations perform badly. The APAR
    provides an option to turn off accessing the stylesheet from the
    file system during the processing of each input message.
    

Local fix

  • Deploy the stylesheet along with the bar file.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM App Connect Enterprise V11.0 and V12.0 and IBM
    Integration Bus V10.0 using the XSLTransform node
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    XSLTransform node has property 'stylesheet cache level' to
    specify the stylesheets to be compiled and cached. But in the
    case of non-deployed style sheets even if the stylesheet is in
    the cache, during the processing of each input message the
    stylesheet file is accessed from the file system. This is to
    check the last modified time of the stylesheet and to determine
    whether the cache contains the correct version of the
    stylesheet. But accessing the stylesheet from the file system
    for each input message can cause performance issues if the file
    operations perform badly.
    

Problem conclusion

  • The product now introduced an environment variable
    'MQSI_XSLT_CACHED_XSLTFILES_MODIFIED_TIME_CHECK_INTERVAL' to
    control the frequency in accessing the stylesheet from the file
    system. This environment variable can be set with values -1,0
    and any positive number.
    
    MQSI_XSLT_CACHED_XSLTFILES_MODIFIED_TIME_CHECK_INTERVAL=0
    (default), existing behaviour of lastModified time check on the
    cached XSLT file during the processing of each input message.
    
    MQSI_XSLT_CACHED_XSLTFILES_MODIFIED_TIME_CHECK_INTERVAL=-1
    completely turns off the lastModified time check on the cached
    XSLT files.
    
    MQSI_XSLT_CACHED_XSLTFILES_MODIFIED_TIME_CHECK_INTERVAL=TimeInte
    rvalInSeconds, say
    MQSI_XSLT_CACHED_XSLTFILES_MODIFIED_TIME_CHECK_INTERVAL=120 then
    after the expiry of every 2 minute, during the processing of the
    message the message flow checks the lastModified time on the
    cached XSLT file.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v10.0      10.0.0.25
    v11.0      11.0.0.15
    v12.0      12.0.3.0
    
    The latest available maintenance can be obtained from:
    http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
    
    If the maintenance level is not yet available,information on
    its planned availability can be found on:
    http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT36793

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0540

  • Reported release

    A00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-05-05

  • Closed date

    2022-03-10

  • Last modified date

    2022-03-11

  • 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

    INTEGRATION BUS

  • Fixed component ID

    5724J0540

Applicable component levels

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0"}]

Document Information

Modified date:
12 March 2022