PQ62489: MD10454- ASYNCHRONOUS NAMING REGISTRATION DURING SERVER STARTUP IS NOT SUPPORTED.

APAR status
Closed as fixed if next.

Error description
An application server CBTEST has 2 instances, CBTESTA1 and
CBTESTA2.  When a J2EE application is added into the server, the
instance comes down, restarts, and naming registration begins.
Before the naming registration completes, the second server
instance comes down restarts, and naming registration begins.
This results in one of the naming registration processes failing
with the messages BBOU0652E NAMING REGISTRATION FAILED FOR
CBTEST and BBOU0006E CB SERIES SERVER CBTESTA1 ENDED ABNORMALLY
REASON=C9C21235.
Local fix
We recommend that the customer proceed strictly
sequential, i.e. if a server is to be modified in a
conversation, then all of its server instances that are up
and running should be stopped first, then the server should
modified using the SM EUI.  After activate has completed, on
server instance of the server should be started to do the
naming registration.  After naming registration has complete
you would start the other server instances of the same server.
This bypass will work in a test environment where a temporary
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V4.0.1 for z/OS and OS/390                   *
****************************************************************
* PROBLEM DESCRIPTION: When an application server with two or  *
*                      more currently running server           *
*                      instances requires naming registration  *
*                      work, a naming registration failure     *
*                      may occur during application server     *
*                      startup.                                *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
After a conversation has been activated that requires naming
registration modifications on an application server, naming
registration failures may occur during server startup of
an application server that has more than one server instance
currently running.  This will produce the following messages:

BBOU0652E NAMING REGISTRATION FAILED FOR SERVER <server_name>
BBOU0006E CB SERIES SERVER <server_name> ENDED ABNORMALLY,
          REASON=<reason_code>.

The naming registration code should be modified to remove these
limitations/restrictions.
Problem conclusion Temporary fix Comments
This APAR is being closed FIN with concurrence from the
submitting customer. A solution to this problem will be
delivered in a WebSphere Application Server for z/OS
and OS/390 release within the next 18 months.
APAR information
APAR number PQ62489
Reported component name WEBSPHERE OS/39
Reported component ID 5655A9800
Reported release 401
Status CLOSED FIN
PE NoPE
HIPER NoHIPER
Submitted date 2002-06-20
Closed date 2002-07-12
Last modified date 2002-07-16

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 #: PQ62489
IBM Group: Software Group
Modified date: Jul 16, 2002