IBM Support

IT17566: ABENDS OR UNEXPECTED RESULTS FROM SHARED ESQL WHEN EXCEPTION IS THROWN PROCESSING FIRST INPUT MESSAGE THROUGH THE MESSAGE FLOW

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Shared ESQL modules are generated at runtime when the first
    message is processed after the deployment.
    
    If an exception is thrown during processing of the first
    message, the ESQL modules and associated artifacts may not be
    successfully generated.
    
    This can cause unexpected results when subsequent messages are
    processed.
    
    In the case of Java Modules called from ESQL this may cause a
    Java Abend.
    
    A similar problem can occur  if there is a processing error in
    an ESQL
    transform owned by a Mapping node.
    

Local fix

  • A redeploy may be required.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of WebSphere Message Broker V8, IBM Integration Bus V9
    and V10 who use the Compute node to call a Java module or use
    the Mapping node with an ESQL custom transform.
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    Shared ESQL modules are generated at runtime when the first
    message is processed after the deployment.
    
    If an exception is thrown during processing of the first
    message, the ESQL modules and associated artifacts may not be
    successfully generated.
    
    This can cause unexpected results when subsequent messages are
    processed.
    
    In the case of Java Modules called from ESQL this may cause a
    Java Abend.
    
    A similar problem can occur  if there is a processing error in
    an ESQL
    transform owned by a Mapping node.
    
    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 now correctly handles problems processing the first
    input message after the deploy of shared ESQL that calls Java,
    or is called from a Mapping node.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v10.0      10.0.0.8
    v8.0       8.0.0.9
    v9.0       9.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

    IT17566

  • Reported component name

    WEB MESSAGE BRO

  • Reported component ID

    5724J0520

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-10-18

  • Closed date

    2017-03-15

  • Last modified date

    2017-03-15

  • 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":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSKM8N","label":"WebSphere Message Broker"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
15 March 2017