PQ92184: SHIP INTERNAL DEFECT FIXES FOR SERVICE LEVEL W502014.

 A fix is available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
Ship internal defect fixes for Service Level W502014.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: APAR PQ92184 addresses the following    *
*                      defect in WebSphere Application Server  *
*                      V5.0 for z/OS:                          *
*                                                              *
*                      (MD19704.1) Various failures in the     *
*                      application server running in a         *
*                      stressed environment.                   *
*                      - ABEND40D/ABENDs40D,                   *
*                        RC=10,COMPON=RTM2 +COMPID=SCRTM.      *
*                      - ABENDs0C4/ABEND0C4 BBOBOA in various  *
*                        methods.                              *
*                      - CORBA::INTERNAL exception with minor  *
*                        code C9C21250.                        *
*                                                              *
*                      (MD19839) Can not start JMS server on   *
*                      second node on Network Deployment (ND). *
*                                                              *
*                      (MD20072) An application server servant *
*                      abends with Abend 40D,RC=10,COMPON=RTM2 *
*                      COMPID=SCRTM. UNRECOVERABLE ABEND       *
*                      FAILURE.                                *
*                                                              *
*                      (MD20201) java.lang.RuntimeException    *
*                      when using SQLJ with cached JDBC        *
*                      Connection handles                      *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
APAR PQ92184 addresses the following defect in WebSphere
Application Server V5.0 for z/OS:

(MD19704.1) A server is configured with security enabled,
and a web application is installed. The server resides in a
server-as-client environment in a highly stressed environment.
A servant region can abend S40D, which signals an out
of storage condition. An application may hang or fail to
process requests with CORBA::INTERNAL exceptions
(minor code C9C21250) appearing in the job output of the
servant. A controller may abend with 0C4 abends in the BBOBOA
DLL.

(MD19839) Federating a second Base AppServer with MQ installed
results in a second JMS Server being created.  The short name of
this second JMS Server is BBOJ001 which is the same as the
first. This doesn't allow the second JMS server to be started
because the short name is not unique.

When attempting to start the second JMS Server, the following
errors can occur -

BBOO0100E WEBSPHERE FOR Z/OS CONTROL PROCESS BBOJ001 FAILED TO
INITIALIZE BECAUSE ANOTHER CONTROL PROCESS OF THE SAME NAME WAS
STARTING.

BBOO0003E WEBSPHERE FOR Z/OS CONTROL PROCESS BBOJ001 ENDED
ABNORMALLY, REASON=C9C22433.
BPXP018I THREAD 1036990000000000, IN PROCESS 50331692, ENDED
WITHOUT BEING UNDUBBED WITH COMPLETION CODE 4FDC3000, AND REASON
CODE 000C0009.
IEF450I BBOJ001 BBOJ001 - ABEND=SDC3 U0000 REASON=000C0009

(MD20072) An application server is configured with security
enabled, localOS registry and a web application is installed
in a server-as-client environment. Eventually, the servant
abends with an UNRECOVERABLE ABEND FAILURE, ABEND=40D,RC=10.

The cause of the failure was due to a storage shortage. The
dump showed BOOOOPI as the main problem. The storage leaks
occurred when the server needed to send a request to
another server. A method was called to build the security
control block, BBOOOPI, with the identity information for the
current thread of execution and pass it to the controller. After
the information was passed to the controller the control block
was "freed" by the freeCredential method. However, this method
does not necessarily free the storage. It will move some
control blocks to a table for reuse. However, the reuse
normally only occurs when a BBOOOPI is copied from the
controller to the servant. These BBOOOPIs are created in the
servant on every outbound request and are never reused.

(MD20201) If a bean caches a JDBC Connection handle across
method invocations, the underlying connection to DB2 will be
disassociated from the handle at the end of the method
invocation.  The handle will be reassociated during the next
method invocation when the handle is first used.

However, if the first thing that the handle is used for is to
execute SQLJ, the handle will fail to reassociate itself with an
underlying connection to DB2.  This will result in a
java.lang.RuntimeException in the joblog of the application
servant region.  The text of the exception message will be
"DB2SQLJConnectedProfile Received Error in Method Constructor:
Unable to resolve the DB2SQLJConnection."
Problem conclusion
APAR PQ92184 fixes the following defect in WebSphere Application
Server V5.0 for z/OS.

(MD19704.1) The 40D abends were caused by storage leaks of the
security  BOOOPI control block or the security execution
environment (SEED) control block. The BBOOPI and SEED storage
leaks were fixed.
The 0C4 abends were caused by the double free of members in the
OutboundUseridInfo object when the server was acting as a
client. The double free was fixed.
The CORBA::INTERNAL exception resulted from a failure to free
NSC tokens from the security identity table in the servant.
Code was added to free the token in the path that was not doing
so.

(MD19839) Fix the JMS Server generation utility to correctly
check for existing short names on Network Deployment and
generate a unique one.

(MD20072) Support was modified to delete these paticular
BBOOOPIs instead of moving them to the reuse table.

(MD20201) The WebSphere JDBC Connection handle has been fixed so
that, if necessary, it will reassociate itself with a connection
to DB2 when used for SQLJ

APAR PQ92184 is associated with SERVICE LEVEL W502014 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PQ92184
Reported component name WEBSPHERE FOR Z
Reported component ID 5655I3500
Reported release 500
Status CLOSED PER
PE NoPE
HIPER YesHIPER
Special Attention NoSpecatt
Submitted date 2004-07-29
Closed date 2004-08-15
Last modified date 2004-09-03

APAR is sysrouted FROM one or more of the following:

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

Modules/Macros
BBOCASYD BBOCASYE BBOCASYH BBOCLCLR BBOCLOCT BBOCLSAC
BBOCLSCC BBOCLSPC BBOCLSSA BBOCLSUE BBOCLSUR BBOCPO
***This field was truncated. To obtain
the full apar record, please contact
your local support center.***    

Publications Referenced

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

Applicable component levels
R500 PSY UQ91441    UP04/08/23 P F408

  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: swg1PQ92184.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 #: PQ92184
IBM Group: Software Group
Modified date: Sep 3, 2004