IBM Support

IT14173: DATAFLOWENGINE ABENDS IF INPUTLOCALENVIRONMENT MBMESSAGE OBJECT IS MODIFIED IN JAVACOMPUTE NODE

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

  • InputLocalEnvironment is not treated as readonly MbMessage
    object in
    JavaCompute Node. This may result in corruption of
    LocalEnvironment
    message tree and may cause crash or abend.
    This may apply to exceptionList also.
    
    Additional Symptom(s) Search Keyword(s):
    

Local fix

  • The JavaComputeNode should use the recommended way to modify
    LocalEnvironment and ExceptionList
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    <div>All users of IBM Intergation Bus V10 and App Connect
    Enterprise v11 who use Java Compute node.</div><div> </div>
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The DataFlowEngine may crash due to parser going out of scope in
    the following conditions
    i. JavaCompute node in flow modifies InputLocalEnvironment
    object and is copied into another message tree
    ii. Flow rollbacks due to failure after the JavaCompute node
    that modifies InputLocalEnvironment
    iii. The copied LocalEnvironment tree is referenced in the
    failure path of the flow
    
    There are a number of resource name changes between WebSphere
    Message Broker and IBM Integration Bus Version 9.0.  For details
    visit
    http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e
    tools.mft.doc/bb23814_.htm
    

Problem conclusion

  • The product is modified to handle the parser scope and does not
    crash due to out of scope object referencing.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v10.0      10.0.0.20
    v11.0      11.0.0.8
    
    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

    IT14173

  • Reported component name

    WEB MESSAGE BRO

  • Reported component ID

    5724J0520

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-03-08

  • Closed date

    2020-04-09

  • Last modified date

    2020-04-09

  • 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

    WEB MESSAGE BRO

  • Fixed component ID

    5724J0520

Applicable component levels

[{"Business Unit":{"code":"BU048","label":"IBM Software"}, "Product":{"code":"SSKM8N","label":"WebSphere Message Broker"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Edition":""}]

Document Information

Modified date:
09 April 2020