PQ54141: 390 LOCAL CLIENT COULDN'T BE NOTIFIED A FAILURE IN CONTROL REGION

APAR status
Closed as fixed if next.

Error description
390 Local client couldn't be notified a failure in CR.
PC(Program Call) was used instead of TCP/IP to connect to CR.
If a J2EE Server CR goes down during processing of a client
request, the failure should be propagated to the client
immediately with an appropriate exception.
*BUT* in our test, when a OS/390 local client was connected to
CR using PC(Program Call) instead of TCP/IP and then the CR
fails, no exception was sent back to the z/OS client. The client
got hang.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V4.0 and V4.0.1 for z/OS and OS/390.         *
****************************************************************
* PROBLEM DESCRIPTION: If a WAS/390 Control Region goes down,  *
*                      local clients will not be notified.     *
*                      The CLIENT_TIMEOUT environment variable *
*                      may be used to cause a COMM_FAILURE     *
*                      exception in this case after the time   *
*                      expires, but if the variable is not set *
*                      the client will hang.                   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
No mechanism exists to notify local clients that the server
has gone away.  Over TCP/IP connections a failure will be
communicated and a COMM_FAILURE exception generated.  The
CLIENT_TIMEOUT environment variable was intended to address
this problem by allowing the client to specify how long it
should wait in the event of a server failure before determining
a problem had occurred.  However, if this variable is not
used, the client will hang forever.  A more robust solution
is desireable.
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.
APAR information
APAR number PQ54141
Reported component name WASKBASE
Reported component ID 5655A9801
Reported release 400
Status CLOSED FIN
PE NoPE
HIPER NoHIPER
Submitted date 2001-11-01
Closed date 2001-12-12
Last modified date 2001-12-12

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 #: PQ54141
IBM Group: Software Group
Modified date: Dec 12, 2001