PQ65264: ORB CLIENT HANGS WHEN A WLM AND SECURITY ENABLED

 A fix is available

4.0.5: WebSphere Application Server Version 4.0 Fix Pack 5 (Version 4.0.5)



APAR status
Closed as program error.

Error description
ORB client hangs when a WLM and Security enabled client is
trying to talk to a WLM adminServer, which is down. This WLM
and Security was unable to switch to another WLM adminServer
because ORB doesn't correctly throw an CORBA.COMM_FAILURE
back to client's WLM component.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users of        *
*                 client ORB with WLM and Security enabled.    *
****************************************************************
* PROBLEM DESCRIPTION: WLM and Security enabled ORB client     *
*                      hangs on operation of                   *
*                      read_com_ibm_ejs_sm_beans_SeriousEvent  *
*                      when one of WLM adminServer was         *
*                      purposely brought down.                 *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The hang is caused by ORB not handling the
CORBA.COMM_FAILURE exception properly and ORB also attempts to
send data on a bad socket.

ORB trace shows client ORB hangs on the following entry and it
is being the last entry as well during operation of
read_com_ibm_ejs_sm_beans_SeriousEvent or other similar
System Managment operation(s).

 8/5/02 15:34:54:316 EDT  68d09ac8 ORBRas        >
com.ibm.CORBA.iiop.ClientRequestImpl ijavaorb P=88428:O=0:CT
Entry invoke(isOneway=false)
Problem conclusion
Added extra catch block to handle CORBA.COMM_FAILURE exception
when the client failed to create a socket.  Since socket is bad,
ORB mistakenly uses this bad socket to attempt to send data
which leads to a hang state.  To prevent this hang, ORB
re-throws this same exception back to the WLM component instead
of sending a message on the failed socket.
Temporary fix Comments
APAR information
APAR number PQ65264
Reported component name WEBSPHERE AES U
Reported component ID 5630A2303
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2002-08-14
Closed date 2002-09-03
Last modified date 2003-04-30

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
ORB          

SRLS

Fix information
Fixed component name WEBSPHERE AES U
Fixed component ID 5630A2303

Applicable component levels
R400 PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ65264
IBM Group: Software Group
Modified date: Apr 30, 2003