PM88131: XA RECOVERY FAILS ON SERVER RESTART

Fixes are available

APAR status

Closed as program error.

Error description

On a server restart following messages are encountered in
SYSPRINT for transactions between WebSphere and CICS using WOLA:
---
BBOA0030E: An exception was raised when Committing a transaction
           with OLA registration OUTTRAN1
BBOO0221W: WTRN0048W: An attempt by the transaction manager to
           call commit on a transactional resource has resulted
           in an XAER_RMFAIL error.
   The resource was com.ibm.ws390.ola.jca.XAResourceImplSac9acf1
---
The CICS log shows following error messages at that timeframe:
---
BBO Fri Apr 19 15:03:08 2013 0000390 BBOA8764E Recovery UOW is
in the wrong state (COMMIT) or wrong waitstate (WAITING) for re
.
So this is the error that is being reported byWebSphere,
and is the reason why the transaction cannot resolve.
.
It was found out by WAS development that it should not be
necessary for WebSphere to wait for the CICS UOW to complete if
it has already been marked for commit or backout on the
transaction recovery path.
.
This APAR has been taken to allow the WebSphere transaction to
finish processing if the CICS UOW has already been marked for
commit or backout.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V8.0 and V8.5                        *
****************************************************************
* PROBLEM DESCRIPTION: Message BBOA0030E is issued repeatedly  *
*                      in the WebSphere servant region log.    *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
During transaction recovery, WebSphere Application Server for
z/OS is attempting to resolve a transaction with CICS
Transaction Server.  The transaction was propagated to CICS
using the WebSphere Optimized Local Adapters (WOLA) connector.
The CICS branch of the transaction has already committed.  The
following message in the CICS log shows this:
BBOA8764E Recovery UOW is in the wrong state (COMMIT) or
wrong waitstate (WAITING) for recovery.
This causes WebSphere to issue the following message:
BBOA0030E: An exception was raised when Committing a
transaction with OLA registration XXXXXX
The outcome of this transaction has already been delivered to
CICS so there is no reason for WebSphere to continue to try to
deliver the outcome.  Eventually CICS will finish committing
its portion of the transaction and the CICS UOW will end.  At
this point WebSphere will detect that the transaction has
finished and will stop trying to deliver the outcome.

Problem conclusion

Code was added to allow WebSphere to detect when the outcome of
a CICS WOLA transaction has already been delivered.

APAR PM88131 is currently targeted for inclusion in  Fix Packs
8.0.0.7 and 8.5.5.1 of WebSphere Application Server.

Please refer to the Recommended Updates page for delivery
information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

In addition, please refer to URL:
http://www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
for Fix Pack PTF information.

Temporary fix

Comments

APAR Information

APAR number
PM88131
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-04-30
Closed date
2013-05-31
Last modified date
2013-05-31

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

R800 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"800","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
11 January 2022

Tips

PM88131: XA RECOVERY FAILS ON SERVER RESTART

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R800 PSY

Document Information

Share your feedback

Need support?