PQ54008: EXCEPTION FROM BEFORE_COMPLETION IS NOT RETURNED TO THE COORDINATOR.

APAR status
Closed as fixed if next.

Error description
The server region BBOTRX1S was cancelled after BBOTRX1A returned
a reply message and before BBOTRX1A received a prepare request.
When the control region BBOTRX1A received prepare request, he
found that the server region had gone, so raised CORBA::INTERNAL
exception. After that, he never returned a reply message to
BBOTRX2A. So the syncpoint processing hang up.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V4.0 for z/OS and OS/390.                    *
****************************************************************
* PROBLEM DESCRIPTION: An attempt to mark a transaction for    *
*                      rollback only after asynchronous RRS    *
*                      backout during transaction pre-prepare  *
*                      can cause assertion failure in the      *
*                      control region. The assertion will be   *
*                      surfaced in the job log of the control  *
*                      region as a BBOU0022E Assertion failed  *
*                      message.                                *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
If a server region in a subordinate node of a transaction abends
during the execution of before_completion, RRS will drive an
asynchronous application backout.  As part of the abend
processing, the ORB will throw a system exception to the caller.
OTS handles system exceptions by marking the current transaction
for rollback only.  Since the current transaction was already
marked for rollback only by RRS, RRS indicates that there was a
UR state error.  When the OTS transaction is in a state of
pre-prepare, this UR state error was unexpected and caused an
assertion failure.
Problem conclusion Temporary fix Comments
This APAR is being closed FIN with concurrence from the
submitting customer. A solution to this problem will be
delivered in a WebSphere Application Server for z/OS
and OS/390 release within the next 18 month.
.
A fix for the problem reported by this APAR has been
provided in PTF UQ58682 of WebSphere Application Server
V4.0.1 for z/OS and OS/390.
APAR information
APAR number PQ54008
Reported component name WASKBASE
Reported component ID 5655A9801
Reported release 400
Status CLOSED FIN
PE NoPE
HIPER NoHIPER
Submitted date 2001-10-30
Closed date 2001-11-15
Last modified date 2002-07-24

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros

Fix information

Applicable component levels
R400 PSN    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ54008
IBM Group: Software Group
Modified date: Jul 24, 2002