IBM Support

IT10122: RESEQUENCE NODE WITH RETRYMECHANISM=FAILURE AND NO SEQUENCE NUMBER CAN FAIL WITH 'EXPIRED SEQUENCE' ERRORS

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

  • When using the Resequence node with a retry mechanism of
    failure and when not using a sequence number, a message
    arriving at the same time as a message sequence is being
    expired can trigger an error and reject the input message when
    it should be accepted.
    
    
    Additional Symptom(s) Search Keyword(s):
    

Local fix

  • Modifying the 'end of sequence' timer can make the error less
    likely to be triggered.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus V9.0 and V10.0 that use the
    Resequence node with the retry mechanism set to 'failure' and
    use the Resequence node to process a sequence of messages
    without a sequence number.
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When the retry mechanism is set to failure, the Resequence node
    allows a message to be missing a sequence number. This is valid
    if all of the incoming messages are already in the correct order
    and allows the Resequence node to be used in a way that will
    collect one sequence of messages behind a failure, while
    allowing all other message sequences to propagate.
    
    In this mode, if a message arrives at the same time as it's
    message sequence is being expired, the incoming message is
    rejected as being part of an expired group, but the message
    should be accepted as the start of a new sequence.
    
    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 for situations when the Resequence
    node is using a retry mechanism of "failure" so that if a
    message in a sequence arrives while that sequence is being
    expired, the sequence expiry is completed and the new message is
    accepted.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    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

    IT10122

  • 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-16

  • Closed date

    2015-08-27

  • Last modified date

    2015-08-27

  • 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