PK21235: When request hits WLM TIMEOUT WITH BBOO0232W MESSAGE. NOT SURE IF THE TRANSACTION COMMITTED/ROLLEDBACK TO THE END USER.

 A fix is available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
Running WebSphere Application Server zOS with control_region_wlm
_dispatch_timeout and transaction_defaultTimeout active,

When a request is in the process of committing the transaction
and meanwhile If the WLM timer hits, the transaction is going
to be committed even If the request comes back to the client as
timed out with a BBOO0232W message resulting Control region
terminating the Servant.

In this situation the end user has no way to identify If the
request resulted in committ/rollback of the transaction.

The timed-out message in the Controller..

STC07217  BBOO0232W A request for Class Name `string`and Method
Name `invoke`, from hostname=161.96.232.231 port=65446, has
timed out.  The servant process associated with the request
will be terminated. Request Id(FFB971A1)
Local fix
Set the control_region_wlm_dispatch_timeout considerably higher
than the transaction_defaultTimeout.
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: The amount of time which elapses        *
*                      between a transaction timeout and the   *
*                      subsequent ABENDEC3/ABENDSEC3 of the    *
*                      associated servant region has changed   *
*                      between WebSphere Application Server    *
*                      for z/OS and OS/390 Version 4 and       *
*                      WebSphere Application Server for z/OS   *
*                      Version 5.                              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When a transaction timeout occurs on WebSphere Application
Server for z/OS and OS/390 Version 4, the associated servant
region is abended immediately with an ABENDEC3/ABENDSEC3.  This
behavior was modified in WebSphere Application Server for z/OS
version 5.  In version 5, the application which timed out is
given an additional period of time (approximately four minutes)
to return control to the container so that the transaction can
be rolled back rather than issuing the abend.  This delay may
be incompatible with retry logic coded by some application
programs, which need to be notified of the impending rollback
immediately.
Problem conclusion
A custom property was added to the transaction service which
allows the delay between the transaction timeout and the
subsequent abend of the servant region to be removed for an
Application Server.

This APAR requires changes to documentation.

NOTE: Periodically, we refresh the documentation on our
Web site, so the changes might have been made before you
read this text. To access the latest on-line
documentation, go to the product library page at:


http://www.ibm.com/software/webservers/appserv/library
.
The following information will be added to the WebSphere
Application Server for z/OS V5.0.x, V5.1, and V6.0.x
Information Centers:

DISABLE_TRANSACTION_TIMEOUT_GRACE_PERIOD
Specifies whether there is a delay between a transaction
timeout and the abnormal ending of the servant region that
was running the transaction.

If you set this value to false, a global transaction that
times out is marked rollback-only. The transaction server
gives the associated application an additional period of time,
approximately four minutes, to complete. If the application
completes in this time, the transaction is rolled back. If
the application does not complete in this time, the
application and associated servant region are ended
abnormally, with an ABENDEC3 or ABENDSEC3 error.

Set this value to true to remove the delay, and abnormally
end the application and servant region immediately.

   Data Type           Boolean
   Acceptable values   true, false
   Default             false

APAR PK21235 is currently targeted for inclusion in SERVICE
LEVEL W502040 of WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PK21235
Reported component name WEBSPHERE FOR Z
Reported component ID 5655I3500
Reported release 500
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2006-03-10
Closed date 2006-04-14
Last modified date 2006-06-03

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:
PK21236 PK21238

Modules/Macros
BBOUBINF          

Publications Referenced

Fix information
Fixed component name WEBSPHERE FOR Z
Fixed component ID 5655I3500

Applicable component levels
R500 PSY UK14466    UP06/05/18 P F605

  Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.


Document Information


Current web document: swg1PK21235.html
Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PK21235
IBM Group: Software Group
Modified date: Jun 3, 2006