PQ68666: SM SERVER REGION (BBOSMSS) FAILS TO START WITH MESSAGE BBOU0652E NAMING REGISTRATION FAILED FOR SERVER CBSYSMGT

APAR status
Closed as unreproducible in next release.

Error description
When starting up WebSphere, after the daemon starts an error
occurs in BBOSMSS. These are the messages from BBOSMSS:
BBOU0021I INITIALIZATION COMPLETE FOR CB SERIES SERVER SYSMGT01.
BBOU0694I NAMING REGISTRATION STARTED FOR SERVER CBSYSMGT
BBOU0698I REGISTERING SERVER CBSYSMGT
BBOU0652E NAMING REGISTRATION FAILED FOR SERVER CBSYSMGT
The was.error.log at that point in time has this:
2002/10/24 19:39:49.198 01 SYSTEM=SYSB SERVER=SYSMGT01
JobName=BBOSMSS ASID=0X0205 PID=0X0100003B
TID=0X16883800 0X000008 c=UNK
./bbomsbo7.cpp+1218 ... BBOU0013W The function
Ism_ScriptingBO_Ism_ConversationBO_Impl::DoNamingRegistration
(const char*,const char*)+1218 raised a user exception
Ism_Scripting::Ism_Conversation::NamingRegistrationFailed
2002/10/24 19:39:49.196 01 SYSTEM=SYSB SERVER=SYSMGT01
JobName=BBOSMSS ASID=0X0205 PID=0X0100003B
TID=0X16883800 0X000008 c=UNK
./bbooreq.cpp+727 ... BBOU0011W The function
CORBA::Request::Request(CORBA::Object_ORBProxy_ptr,char*,
CORBA::Flags) +727 raised CORBA system exception
CORBA::OBJECT_NOT_EXIST. Error code is C9C21047
.
The Naming Registration failure is occurring because the Systems
Management server, BBOSMSS, is trying to deregister an OTS
Factory object prior to the Naming Server being initialized.
The Naming Server handles Naming Registration for objects that
reside in the CORBA piece of the WebSphere name space.
Local fix
Naming Registration errors can occur for many reasons and for
many servers.  To confirm you situation matches this APAR,
please run the following SQL queries.  If the name of your
Systems Management server is not CBSYSMGT, you will need to
substitute your customized name for CBSYSMGT in all the SQL
statements below.
.
SELECT ACTIVE_IMAGE_LEVEL FROM BBO.BBOMT00_MASTER;
--
SELECT SERVER_GRP_NAME, HEX(DO_NM_REGISTRATION),SERVER_GRP_LEVEL
FROM BBO.BBOMT06_ACT_SG
WHERE SERVER_GRP_NAME='CBSYSMGT'
ORDER BY SERVER_GRP_LEVEL;
--
SELECT *
FROM BBO.BBOMT84_NAMREG
WHERE SERVER_NAME='CBSYSMGT';
.
The value of ACTIVE_IMAGE_LEVEL from the first query is the
number needed for qualify which row to look at for the value
of SERVER_GRP_LEVEL from the second query.
.
In the results of the third query, look for
IS_ACTIVATED = 01
IS_CB_SERVER = 01
TF_REGISTRATION = 00
Name to register:
CBSYSMGT*CB_Base_NC_NonTransactional_Container*COSControlFactory
  cosFactoryBranch
.
To make sure that this was the only Naming Registration piece
of work to do, there should only be 1 row resulting from that
first SQL command.  If the the above all matches, then you can
go ahead and run this SQL statement to remove the entry and
thus avoid the error message:
.
DELETE FROM BBO.BBOMT84_NAMREG WHERE SERVER_NAME='CBSYSMGT';
.
Once you issue this SQL statement, upon the next start of the
WebSphere environment, you should no longer see the message:
BBOU0652E NAMING REGISTRATION FAILED FOR SERVER CBSYSMGT
If there was more than one row returned or you are not sure
about the output from any of the SQL statements, please contact
WebSphere support to determine if it is ok to run the DELETE
SQL statement.
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V4.0.1 for z/OS and OS/390.                  *
****************************************************************
* PROBLEM DESCRIPTION: Sysment Management server region        *
*                      BBOSMSS) fails to start with message:   *
*                      BBOU0652E NAMING REGISTRATION FAILED    *
*                      FOR SERVER CBSYSMGT                     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When starting up WebSphere, after the daemon starts an error
occurs in BBOSMSS. These are the messages from BBOSMSS:

BBOU0021I INITIALIZATION COMPLETE FOR CB SERIES SERVER SYSMGT01.
BBOU0694I NAMING REGISTRATION STARTED FOR SERVER CBSYSMGT
BBOU0698I REGISTERING SERVER CBSYSMGT
BBOU0652E NAMING REGISTRATION FAILED FOR SERVER CBSYSMGT

The was.error.log at that point in time has this:
2002/10/24 19:39:49.198 01 SYSTEM=SYSB SERVER=SYSMGT01
JobName=BBOSMSS ASID=0X0205 PID=0X0100003B
TID=0X16883800 0X000008 c=UNK
./bbomsbo7.cpp+1218 ... BBOU0013W The function
Ism_ScriptingBO_Ism_ConversationBO_Impl::DoNamingRegistration
(const char*,const char*)+1218 raised a user exception
Ism_Scripting::Ism_Conversation::NamingRegistrationFailed

2002/10/24 19:39:49.196 01 SYSTEM=SYSB SERVER=SYSMGT01
JobName=BBOSMSS ASID=0X0205 PID=0X0100003B
TID=0X16883800 0X000008 c=UNK
./bbooreq.cpp+727 ... BBOU0011W The function
CORBA::Request::Request(CORBA::Object_ORBProxy_ptr,char*,
CORBA::Flags) +727 raised CORBA system exception
CORBA::OBJECT_NOT_EXIST. Error code is C9C21047
Problem conclusion Temporary fix Comments
This is a timing issue.  The Naming Registration failure is
occurring because the Systems Management server, BBOSMSS, is
trying to deregister an OTS Factory object prior to the Naming
Server being initialized.  The Naming Server handles Naming
Registration for objects that reside in the CORBA piece of the
WebSphere name space.

The APAR is being closed UR1 with the consent of the reporting
customer.
APAR information
APAR number PQ68666
Reported component name WASKBASE
Reported component ID 5655A9801
Reported release 401
Status CLOSED UR1
PE NoPE
HIPER NoHIPER
Submitted date 2002-11-27
Closed date 2003-01-13
Last modified date 2003-01-13

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros

Fix information
Fixed component name WASKBASE
Fixed component ID 5655A9801

Applicable component levels
R401 PSN    UP


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 #: PQ68666
IBM Group: Software Group
Modified date: Jan 13, 2003