PQ51890: THIS APAR ADDRESSES DEFECTS IN WEBSPHERE APPLICATION SERVER V4.0 FOR Z/OS AND OS/390.

 A fix may be available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
This APAR addresses defects in WebSphere Application Server
V4.0 for z/OS and OS/390.
Additional Symptoms:
When starting an application server, you may see ABEND0C4 in
BBOLRT + x'30C64', due to the corruption of the current.env
file for the application server.  (the extra equal signs '='
at the end of the current.env)
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V4.0 for z/OS and OS/390.                    *
****************************************************************
* PROBLEM DESCRIPTION: APAR PQ51890 addresses various problems *
*                      in WebSphere Application Server V4.0    *
*                      for z/OS and OS/390.                    *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
APAR PQ51890 addresses the following problems in
WebSphere Application Server V4.0 for z/OS and OS/390:

Message BBOU0678I is issued with incorrect GSS return codes
and text if GSS API gss_aquire_cred() fails. This is because
the GSS API gss_release_name() is called before issuing the
message, and the GSS major and minor codes will have changed.
Also, this code is not using the correct method to format and
issue the message.

When an RRS enabled resource manager (such as DB2) is accessed
in an environment that does not support two-phase transaction
coordination (ie. a method executing with a NotSupported
transaction attribute), the resource manager is directed to
commit any pending work prior to the completion of the method.
This is not the correct behavior. The correct behavior is to
rollback any uncommitted local transactions. If an application
requires the work executed by a resource manager to be
committed, the application should call the resoure manager
specific commit verb.

A Client with an expired CERTAUTH certificate can fail with a
SIGSEGV ABEND. When the client attempted to connect to the
server using SSL, a secure_socket_init function call was issued.
Since the certificate authority certificate was expired, the
function call failed. Later, the code checked a pointer to the
certificate returned. There was no certificate and the field
happened to contain some garbage data, when the code tried to
reference data pointed to, the abend occurred.

The current.env file associated with a server instance can
become corrupted whenever the number of user-defined
environmental variable specified is equal to 10*n+9 (i.e.,
19, 29, 39 etc.). This corruption can occur whenever WebSphere
writes the evironment files, i.e., during bootstrap phase1,
activate and prepare for coldstart. If the number of
user-defined environmental variables is 10*n+9, then the
environment file gets corrupted with the two last lines
containing just '='. The reason is that in this case the code
sets the sequence length erroneously for the SEQUENCE_String
that contains the environment variable/value pairs. The two
lines containing just '=' lead in turn to a protection exception
(ABEND0C4/ABENDS0C4) during server startup.

A storage leak of four to five IORs per global
transaction exists in WebSphere. Each IOR is 1K in size.

Synchronization objects are registered with the JTA transaction
manager by the container to help manage the life cycle of some
bean types. Prior to this service, the recently completed
transaction would remain associated with the thread and would be
returned to callers of the getTransaction method.  Depending on
the bean type and application implementation, this could result
in an attempt to register a synchronization object.  This
registration would fail with an IllegalStateException. An
example where this scenario could occur would be during the
execution of afterCompletion on a stateful session bean (that
has implemented the SessionSynchronization interface) during
an attempt to use JDBC.
Problem conclusion
APAR PQ51890 provides the following problem resolution:

The code for handling a failure from gss_acquire_cred()
was modified to issue MSBBOU0678I before starting cleanup
processing, and also to issue the message using the correct
Kerberos GSS-API processing method.

At the end of a method dispatch in a local transaction
environment, the RRS enabled resource managers are now directed
to roll back the work associated with their interests.

Module bbocsess.cpp was modified to initialize the pointer
to the returned certificate before calling the
secure_socket_init function.

The indexing error in environment variable handling in module
bbomib10.cpp has been fixed thus eliminating the corruption
of the current.env file.

Module bbottf.cpp has been modified to release the IORs
associated with a global transaction.

The representation of the recently completed transaction is now
removed from the thread of execution prior to driving the
registered Synchronization objects for afterCompletion.

APAR PQ51890 is associated with SERVICE LEVEL W400041 of
WebSphere Application Server V4.0 for z/OS and OS/390.
Temporary fix Comments
 **** PE01/10/15 FIX IN ERROR. SEE APAR 
PQ53149  FOR DESCRIPTION
 **** PE02/01/16 PTF IN ERROR. SEE APAR 
PQ56471  FOR DESCRIPTION
APAR information
APAR number PQ51890
Reported component name WASKBASE
Reported component ID 5655A9801
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2001-08-28
Closed date 2001-09-24
Last modified date 2002-01-17

APAR is sysrouted FROM one or more of the following:

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

Modules/Macros
BBOMCDM BBOMIB10 BBOMSCCO BBOMSCJ2 BBOMSCMD BBOMSCMO
BBOMSCO BBOMSCSR BBOSSESS BBOSSSKR BBOTTF BBOUBINF
BBOZ0812 BBOZ0813        

Fix information
Fixed component name WASKBASE
Fixed component ID 5655A9801

Applicable component levels
R400 PSY UQ58049    UP01/09/28 P F109

  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


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ51890
IBM Group: Software Group
Modified date: Jan 17, 2002