PQ62552: NAMING REGISTRATION FAILURE FOR MISSING CLASS IN HOME DID NOT GIVE MESSAGE BBOU0772E OR EQUIVALENT

 A fix may be available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
A Naming Registration failure error message is needed when a
missing class on a home causes createHome method part of Naming
Registration to fail.  This could be seen with a
java.lang.NoClassDefFoundError exception in the job output of
the application server server region.  With service level
W401062 or higher, you will see a Naming Registration exception
in the WAS error log, and exception information in job
outputs but no BBOUxxxxE error message.
For example, in the WAS error log:
.
2002/06/21 23:43:52.882 01 SYSTEM=SY1 SERVER=SYSMGT01
           PID=0X05000018 TID=0X260D8800 0X000007  c=UNK
     ./bbomsbo7.cpp+2130 ... BBOU0013W The function
     registerComponentNamingRegistrationEntry(
     Ism_NamingRegistrationEntry&,SMO_ptr)+2130 raised a user
     exception
     Ism_Scripting::Ism_Conversation::NamingRegistrationFailed.
.
There will also be exception traces in the Systems Management
server region job output (BBOSMSS):
.
Trace: 2002/06/21 23:43:52.882 01 t=9E4558 c=UNK key=P8
  (080F7026)
  Description: Server Management Trace Info
  Method Name:
    registerComponentNamingRegistrationEntry(
    Ism_NamingRegistrationEntry&,SMO_ptr)
  ApplicationName: PhoneBookSessionApp
  ModuleName: PhoneBookSessionEJB.jar
  ComponentName: PhoneBookSession
  JNDIName: /PhoneBookSessionHome
  Home not creatable:
Trace: 2002/06/21 23:43:52.882 01 t=9E4558 c=UNK key=P8
  (00000006)
  Description: Throw CORBA user exception
  exception id:
     Ism_Scripting::Ism_Conversation::NamingRegistrationFailed
  from file: ./bbomsbo7.cpp
  at line: 2130
Trace: 2002/06/21 23:43:52.883 01 t=9E4558 c=UNK key=P8
  (080F7027)
  Description: Server Management Trace Info
  Method Name:
    registerComponentNamingRegistrationEntry(
    Ism_NamingRegistrationEntry&,SMO_ptr)
  ApplicationName: PhoneBookSessionApp
  ModuleName: PhoneBookSessionEJB.jar
  ComponentName: PhoneBookSession
  JNDIName: /PhoneBookSessionHome
  Exception occured while trying to register:
.
In the job output of BBOSMSS and the server region of the
application server, there are messages indicating Naming
Registration started, BBOU0694I, and completed, BBOU0695I,
but none indicating there was a failure.
Local fix
Look in job outputs for Systems Management server region
(BBOSMSS), application server server region, and the WAS error
log to detect the Naming Registration failure.
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V4.0.1 for z/OS and OS/390                   *
****************************************************************
* PROBLEM DESCRIPTION: Naming registration errors caused by a  *
*                      failure to create the home for a J2EE   *
*                      component are not reported with the     *
*                      BBOU0772E error message.                *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
APAR 
PQ51713 changed the manner in which naming registration
errors are handled on WebSphere Application Server V4.0.1 for
z/OS and OS/390. Prior to 
PQ51713, any errors that occurred
during the naming registration process would cause an
application server to ABEND. 
PQ51713 modified this behavior to
allow the application server to keep running and to report
BBOU0772E error messages to the Systems Management (SM) server
region log for each naming registration error that occurred
at the J2EE component level.

During naming registration for a J2EE component, however, it
is also possible that a naming registration error can occur
due to a failure to create the component home. The fix for

PQ51713 did not address this particular issue, and a failure
to create a J2EE component home did not report the BBOU0772E
error message.
Problem conclusion
The product code was modified to generate the BBOU0772E error
message for all naming registration errors that can occur when
registering a J2EE component, including the failure to create
the component home.

A new error message, BBOU0812E, was created to report that
one or more naming registration errors occurred on a particular
application server during naming registration.  This message
appears in the application server control region logs.

The following publication was revised as a result
of APAR PQ62552:
_______________________________________________________________
WebSphere Application Server V4.0.1 for z/OS and OS/390
Messages and Diagnosis
GA22-7837-04
_______________________________________________________________

NOTE: Periodically, we refresh the documentation on our
Web site, so the changes might have been made before you
read this text. To access the latest on-line
documentation, go to the product library page at:


http://www.ibm.com/software/webservers/appserv/

The change will be to Chapter 13 and will read:

BBOU0812E NAMING REGISTRATION ERROR(S) OCCURRED FOR ONE OR MORE
APPLICATIONS ON SERVER string
Explanation: During naming registration for the specified
server, naming registration errors occurred for one or more of
the applications installed on the server.
User Response: Check accompanying messages in the job log of the
System Management server region that processed naming
registration for more details about which applications caused
the naming registration errors.  Check server region logs for
the specified server for detailed information about the errors.

APAR PQ62552 is associated with SERVICE LEVEL W401084 of
WebSphere Application Server V4.0.1 for z/OS and OS/390.
Temporary fix Comments
APAR information
APAR number PQ62552
Reported component name WASKBASE
Reported component ID 5655A9801
Reported release 401
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2002-06-24
Closed date 2002-07-17
Last modified date 2002-08-04

APAR is sysrouted FROM one or more of the following:

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

Modules/Macros
BBOIROOT BBOJJU BBOMBOOT BBOMDDLI BBOMDDLO BBOMDDLV
BBOMDDLX BBOMDDLZ BBOMGADM BBOMIB80 BBOMICP BBOMIDO
BBOMRDO BBOMSBOI BBOMSBOS BBOMSBO1 BBOMSBO2 BBOMSBO3
BBOMSBO4 BBOMSBO5 BBOMSBO6 BBOMSBO7 BBOMSBO8 BBOMSCPI
BBOMSCRS BBOMSD51 BBOMSD90 BBOMSMOI BBOMSMOS BBOMUTIL
BBOOBOAI BBOOBOAT BBOOORB BBOOSMOI BBOSM BBOUBINF
BBOUENUS BBOZ0769 BBOZ0813 BBOZ0814    

Fix information
Fixed component name WASKBASE
Fixed component ID 5655A9801

Applicable component levels
R401 PSY UQ68187    UP02/07/22 P F207

  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 #: PQ62552
IBM Group: Software Group
Modified date: Aug 4, 2002