IBM Support

IC64931: THE DATA HANDLER PRIMITIVE'S FAIL TERMINAL IS NOT INVOKED IN SOME FAILURE SCENARIOS.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In some failure scenarios, the Fail terminal of the Data Handler
    primitive may not be invoked, when it should be.  The user may
    instead encounter a NullPointerException.  This
    NullPointerException is the result of some failure information
    not being retrievable from the message which entered the Input
    terminal of the Data Handler primitive.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of WebSphere Enterprise Service Bus    *
    *                 and WebSphere Process Server v6.2 who are    *
    *                 using a Data Handler primitive.              *
    ****************************************************************
    * PROBLEM DESCRIPTION: In some failure scenarios, the Fail     *
    *                      terminal of the Data Handler            *
    *                      primitive may not be invoked when it    *
    *                      should be. The user may instead         *
    *                      encounter a NullPointerException.       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    In some failure scenarios, the Fail terminal of the Data
    Handler primitive may not be invoked when it should be. The
    user may instead encounter a NullPointerException. This
    NullPointerException is the result of some failure information
    not being retrievable from the message which entered the Input
    terminal of the Data Handler primitive.
    

Problem conclusion

  • The code was modified such that this problem no longer occurs
    
    There are no known side effects associated with this fix.
    There is no known alternative workaround should you encounter
    this problem.
    
    This code fix was targeted to be included in the following fix
    packs:
    
         6.2.0 Fix Pack 3 (v6.2.0.3)
         7.0.0 Fix Pack 2 (v7.0.0.2)
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC64931

  • Reported component name

    WEB ESB FOR WIN

  • Reported component ID

    5724I8200

  • Reported release

    620

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-12-03

  • Closed date

    2010-01-26

  • Last modified date

    2010-04-22

  • 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 ESB FOR WIN

  • Fixed component ID

    5724I8200

Applicable component levels

  • R100 PSN

       UP

  • R200 PSN

       UP

  • R300 PSN

       UP

  • R612 PSN

       UP

  • R620 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7J6S","label":"WebSphere Enterprise Service Bus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.2","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
30 March 2023