IBM Support

PI69684: MESSAGE PROCESSED BY NOT_SUPPORTED MDB LISTENING IN SR USING BINDINGS MODE REMAINS ON DESTINATION

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When an MDB is configured with a transaction attribute of
    NOT_SUPPORTED for a WMQ provider in bindings mode for a
    non-durable subscription, the message remains on the Topic
    despite having been processed by the MDB.
    
    Pre APAR PI62603 this would also result in the servant region
    terminating with the following messages:
    
    BBOT0004E: RRS SERVICE ATRBACK FAILED WITH RETURN
    CODE=731
    BBOO0222I: WTRN0108I: ATRABAK. Interceptor. Invalid RRS return
    code:
    731, ...
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  WebSphere Application Server users of       *
    *                  Message Driven Beans listening in the       *
    *                  servant region using bindings mode.         *
    ****************************************************************
    * PROBLEM DESCRIPTION: Message not removed from destination    *
    *                      when MDB listening in the servant       *
    *                      region in bindings mode using Local     *
    *                      Transaction.                            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A change to messaging component for MDBs listening in the
    control region was incorrectly scoped changing the behavior of
    the listening in the servant region code path when the MDB has
    a transaction attribute of NOT_SUPPORTED.
    As a result a client acknowledgment mode was used instead of
    auto acknowledge and the RRS unit of recovery under which the
    message was received from the destination was not registered
    with the Local Transaction Containment and was not completed
    at the LTC boundary.  The transaction service interceptor
    detects the presence of the unit of recovery with outstanding
    interests on the thread during response processing of the
    dispatch to process the work in the servant region and so
    performs a rollback on the RRS unit of recovery.
    

Problem conclusion

Temporary fix

  • If the Message Driven Bean can support a Global Transaction,
    then enabling a global transaction in the Message Driven Bean
    will avoid this issue.
    

Comments

APAR Information

  • APAR number

    PI69684

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-09-23

  • Closed date

    2017-02-28

  • Last modified date

    2017-02-28

  • 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

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
19 October 2021