PK68783: CONTROLLER GETS BBOO0327I IIOP REQUEST TIMEOUT FOR INTERNAL SERVER WORK WHEN WORK IS QUEUED TO A DEAD SERVANT.

 A specific fix for this item is not yet available electronically

This record will be updated with a link to the fix if the APAR is new.
For APARs older than 365 days, contact your support center.



APAR status
Closed as program error.

Error description
The controller received the iiop timeouts like:

BBOO0327I IIOP REQUEST TIMEOUT:
(0000):(FA54E353):(00000805):(00000000):():():(2008/04/09
09:31:36.817239):():(com.ibm.ws.odc.ws390.proxy.servant.ODCServa
ntProxyImpl):(handleProxiedEvents):(Local to this
Server):():():()

BBOO0327I IIOP REQUEST TIMEOUT:
(0000):(FA54E2DC):(00000805):(00000000):():():(2008/04/09
09:31:58.506569):():(com.ibm.ws.cluster.zos.SRDescriptionManager
Callback):(update):(Local to this Server):():():()

The problem here is that the controller is queuing the requests
to an old servant that is not completely down. That servant is
incapable of processing any requests and therefore the timeouts
occur.

This apar will address this problem.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V6.1 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: "BBOO0327I IIOP REQUEST TIMEOUT"        *
*                      message appears in the WebSphere        *
*                      Application Server for z/OS Controller  *
*                      joblog.                                 *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The WebSphere Application Server for z/OS Controller queues work
that will be picked up and processed by a Servant.  The
Controller does not queue work to Servant regions that have
been terminated, however during the period of time from when an
abnormal termination of a Servant is requested and when that
Servant actually finishes terminating, the Controller can still
queue work to it.

A Servant that is in the process of abnormally terminating
cannot process work, and therefore any work that is queued to
it will eventually result in the Controller seeing the
"BBOO0327I IIOP REQUEST TIMEOUT" message.
Problem conclusion
The Controller was modified to no longer queue work to a Servant
which is in the process of abnormally terminating.

APAR PK68783 is currently targeted for inclusion in Service
Level (Fix Pack) 6.1.0.23 of WebSphere Application Server V6.1
for z/OS.

Please refer to URL:
//www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
for Fix Pack availability.
Temporary fix Comments
APAR information
APAR number PK68783
Reported component name WEBSPHERE FOR Z
Reported component ID 5655I3500
Reported release 610
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2008-07-09
Closed date 2008-09-22
Last modified date 2008-11-18

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:
PK75951

Modules/Macros

Publications Referenced

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

Applicable component levels
R500 PSN    UP
R601 PSN    UP
R610 PSY    UP
R700 PSY    UP


Document Information


Current web document: swg1PK68783.html
Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 610
Software edition:
Reference #: PK68783
IBM Group: Software Group
Modified date: Nov 18, 2008