IBM Support

IT25034: MESSAGES REMAIN ON SYSTEM.BROKER.ADAPTER.PROCESSED QUEUE AFTER ERROR PROCESSING SAP MESSAGE

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 a SAPInput node receives an asynchronous IDOC, BAPI or ALE
    message, IBM Integration Bus processes
     the input under transaction control, and maintains the state of
    the SAP transaction in an WebSphere MQ
     Message on a queue called SYSTEM.BROKER.ADAPTER.PROCESSED.
    
    This queue is alternatively referred to as the TID (Transaction
    ID) store.  If an error occurs during processing
    of the SAP input  in the message flow, the associated
    transaction state message  may remain in the TID store,
     and the queue depth will build on  the
    SYSYTEM.BROKER.ADAPTER.PROCESSED queue.
    
     These messages then need to be manually removed.
    
    Additional Symptom(s) Search Keyword(s):
    SAP,IDOC,ALE,BAPI,SYSTEM.BROKER.ADAPTER.PROCESSED,TID
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of the SAPInput node receiving asynchronous SAP BAPI,
    IDOC or ALE messages.
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When a SAPInput node receives an asynchronous IDOC, BAPI or ALE
    message, IBM Integration Bus processes the input under
    transaction control, and maintains the state of the SAP
    transaction in an WebSphere MQ Message on a queue called
    SYSTEM.BROKER.ADAPTER.PROCESSED.
    
    This queue is alternatively referred to as the TID (Transaction
    ID) store.  If an error occurs during processing of the SAP
    input  in the message flow, the associated transaction state
    message  may remain in the TID store,
     and the queue depth will build on  the
    SYSYTEM.BROKER.ADAPTER.PROCESSED queue.
    
    These messages need to be manually removed.
    

Problem conclusion

  • The product has been modified to automatically remove
    transaction status messages from the TID store (
    SYSTEM.BROKER.ADAPTER.PROCESSED queue) if an error occurs during
    message flow processing.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v10.0      10.0.0.14
    v11.0      11.0.0.4
    
    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

    IT25034

  • 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

    2018-05-10

  • Closed date

    2019-04-04

  • Last modified date

    2019-04-04

  • 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

[{"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":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
04 April 2019