PQ68823: THIS APAR ADDRESSES DEFECTS IN WEBSPHERE APPLICATION SERVER V4.0.1 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.1 for z/OS and OS/390.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V4.0.1 for z/OS and OS/390                   *
****************************************************************
* PROBLEM DESCRIPTION: APAR PQ68823 addresses various problems *
*                      in WebSphere Application Server V4.0.1  *
*                      for z/OS and OS/390.                    *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
APAR PQ68823 addresses the following problems in
WebSphere Application Server V4.0.1 for z/OS and OS/390:

(MD14826) When driving the method 'flush()' on EJBCacheControl,
applications recieve a NullPointerException. The exception
occurs because an internal array of BeanOs currently enlisted in
the transaction is not populated correctly. This array is used
to drive an ejbStore operation on each BeanO in the tranaction.
Since the array of BeanOs was not created properly, it contains
nulls which raise the NullPointerException.

(MD14989) If naming registration errors are encountered during
server startup of a J2EE application, due to problems like
server classpath/libpath errors, LDAP errors, WLM application
environments not setup or setup incorrectly, the user has to
redeploy the application to retry naming registration. In cases
of customization steps this requires deletion/reinstallation of
a newly defined server for the RemoteWebContainer application to
be redeployed. This behaviour is due to the fact that the
information maintained in the database that indicates naming
work is required on a server startup is reset regardless of
whether naming registration succeeded or failed.

(MD14995) ABENDS0C1/ABEND0C1 or ABENDS0C4/ABEND0C4 in module
BBOOORBP when Kerberos is being used. The dumps all indicated a
problem in ExtractIdOpi(), when a check is made for the X500NAME
information for an existing OPI for a Kerberos user. In the case
of a Kerberos client, the OPI is copied from the control region
and does not contain an ACEE. In this case, further checks to
match on the Kerberos principal in the ACEE will fail with the
reported abends.
Problem conclusion
APAR PQ68823 provides the following problem resolution:

(MD14826) Support was modified to populated the internal array
of BeanOs correctly which allowed the calls to store to succeed.

(MD14989) Support has been modified to not require a
redeployment of the application to retry naming registration.
In cases where the errors are not encountered due to problems
with the application, the problem can be fixed and server
startup will cause naming registration to be retried.
Redeployment of the application will also cause naming
registration to be retried on server startup. In cases where
naming registration errors occurred due to the application, like
an invalid JNDI name, the following message will be displayed on
server startup, till the problem is fixed and the application is
redeployed or deleted:
BBOU0772E NAMING REGISTRATION FAILED FOR COMPONENT
          <component_name> IN APPLICATION <app_name> ON SERVER
          <server_name>.  THIS APPLICATION WILL NOT BE AVAILABLE
          UNTIL IT IS REINSTALLED WITH THE NAMING ERROR FIXED
          FOR THE COMPONENT.

(MD14995) ExtractIdOpi() was modified to NOT check for X500NAME
in the case where there is no ACEE present. Support will allow
an OPI match if there was no principal name passed to the check.
A similar problem was fixed in GetNSCFromSSAIS() which does the
same search on the active identity queue.

APAR PQ68823 is associated with SERVICE LEVEL W401406 of
WebSphere Application Server V4.0.1 for z/OS and OS/390.
Temporary fix Comments
APAR information
APAR number PQ68823
Reported component name WASKBASE
Reported component ID 5655A9801
Reported release 401
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2002-12-04
Closed date 2002-12-10
Last modified date 2003-01-04

APAR is sysrouted FROM one or more of the following:

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

Modules/Macros
BBOMSD90 BBOUBINF BBOZ0786 BBOZ0812 BBOZ0813 BBOZ0814
BBOZ0916 BBOZ0917 BBOZ0918 BBOZ0919 BBOZ0920 BBOZ0921
BBOZ0922 BBOZ0923 BBOZ0924 BBOZ0925 BBOZ0926 BBOZ0927
BBOZ0928 BBOZ0929 BBOZ0930 BBOZ0931 BBOZ0932 BBOZ0933
BBOZ0987 BBOZ0988 BBOZ1003 BBOZ1004 BBOZ1005 BBO3ACEE
BBO3BEGC BBO3CTXM BBO3CTXP BBO3CTXX BBO3ENDC BBO3ENQP
BBO3FRES BBO3GETS BBO3PCBA BBO3PCBT BBO3SETS BBO3SRVP
BBO3SSAF BBO3SSFP BBO3SWCH      

Fix information
Fixed component name WASKBASE
Fixed component ID 5655A9801

Applicable component levels
R401 PSY UQ72501    UP02/12/17 P F212

  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: 401
Software edition:
Reference #: PQ68823
IBM Group: Software Group
Modified date: Jan 4, 2003