IBM Support

PH29128: MIS-IDENTIFICATION OF IBM MQ JMS PROVIDER

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

  • "javax.transaction.SystemException: ATRBEG Failed, RC = 1841"
    
    Application handling  MDB of the BMT method,
    receives "javax.transaction.SystemException: ATRBEG Failed, RC
    = 1841"
    
    Root cause is application is listening in the Servant Region
    rather than Control Region due to WebSphere code defect.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V8.5 for z/OS                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: Attempting to process a message         *
    *                      within a BMT MDB results in a           *
    *                      SystemException being thrown and the    *
    *                      message rolled back.                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Using the IBM MQ JMS provider would normally result in the
    message listener running in the Control Region, while the MDB
    would be running in the Servant Region.  However, the JMS
    provider was mis-identified as being non-IBM.  This caused all
    listener and MDB processing to be deferred to the Servant
    Region, resulting in the failure of the BMT processing.
    

Problem conclusion

  • Change to correctly identify the IBM MQ JMS Provider.
    
    The fix for this APAR is targeted for inclusion in fix pack
    8.5.5.19 For more information, see 'Recommended Updates for
    WebSphere Application Server':
    https://www.ibm.com/support/pages/node/715553
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH29128

  • 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

    2020-09-03

  • Closed date

    2020-10-07

  • Last modified date

    2020-10-07

  • APAR is sysrouted FROM one or more of the following:

    PI77007

  • 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

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

Document Information

Modified date:
08 October 2020