IBM Support

IT10014: INTEGRATION SERVER ABENDS STARTING MESSAGE FLOWS WITH SUBFLOWS THAT INCLUDE COMPLEX ESQL

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

  • <html>Starting a set of message flows that use the same complex
    ESQL files, one at a time, can cause the integration server
    running them to terminate. This only  occurs if the message
    flows that are already started are under load when another
    stopped message flow using the same ESQL is started. Starting
    all message flows or stopping all flows at the same time does
    not cause this issue. When the issue occurs the terminated
    server will generate an abend file.
    </html>
    

Local fix

  • <html>none
    </html>
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of deployable ESQL in IBM Integration Bus V9.
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    A situation exists where certain ESQL statements (such as SELECT
    statements) are not thread safe during an initialisation process
    that occurs on the first message through a node that uses those
    ESQL statements.
    
    During startup, an integration server can crash if a large
    amount of deployable ESQL is going through this initialisation
    process whilst multiple message flows are starting, and those
    message flows are immediately processing messages when they
    start.
    
    <i>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</i>
    

Problem conclusion

  • ESQL initialisation code has been modified to remove a large
    amount of work that occurs during first message through. That
    work has been moved back into startup/deployment time when
    message flows are not yet started, and therefore the problem
    cannot occur.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.0       9.0.0.5
    
    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

    IT10014

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0530

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-07-10

  • Closed date

    2016-01-08

  • Last modified date

    2016-01-08

  • 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

    5724J0530

Applicable component levels

  • R900 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
23 March 2020