IBM Support

IT10486: RESEQUENCE NODE WITH A DEFINED END OF SEQUENCE MAY LOOSE COLLECTIONS ON A RESTART

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If the resequence node has an explicit end of sequence (either
    a specific sequence number or a predicate), and the resequence
    node is still propagating a message to the out terminal when
    the last message in the sequence arrives, the node may store
    the incorrect state message to the persistent store. If the
    flow restarts at this point then the message collection may not
    be recovered properly.
    

Local fix

  • If the message sequence is such that the resequence node can
    use the end of sequence timeout values then use those instead.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus V9.0 and V10.0 that use the
    Resequence node with a message sequence that has a defined end
    of sequence ('literal' or 'predicate').
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When the Resequence node receives an input message or propagates
    a message downstream, it writes it's internal state to
    persistent storage.
    
    If the Resequence node receives the last message in a message
    sequence, and the message flow is stopped before it has
    completed propagating all the message sequence, then the
    Resequence node will write an incorrect state to persistent
    storage.
    
    When the Resequence node is restarted, it will not read that
    state from persistent storage, which results in the message
    sequence being ignored by the Resequence node.
    
    Scenarios that constitute the message flow stopping include:
    - Stopping the message flow or Application
    - Stopping the Integration Node or Integration Server
    - Redeploying the message flow or Application
    - Reloading the Integration Server
    
    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 has been changed so that the correct state is
    written to persistent storage after the last message in the
    message sequence is read in.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.0       7.0.0.8
    v8.0       8.0.0.7
    v9.0       9.0.0.4
    v10.0      10.0.0.2
    
    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

    IT10486

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0530

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-08-04

  • Closed date

    2015-08-27

  • Last modified date

    2016-05-05

  • 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