PQ62188: NAMING EXCEPTIONS AND WARNINGS ARE THROWN WHEN THE NANNY IS WAITING FOR THE ADMIN SERVER TO STARTUP IN THE NAMESERVICES.

 Fixes are available

4.0.5: WebSphere Application Server Version 4.0 Fix Pack 5 (Version 4.0.5)
System Management Component Cumulative Fix for 4.0.2/4.0.3/4.0.4 /4.0.5



APAR status
Closed as program error.

Error description
Problem:
WebSphere 4.0.3 (not seen in earlier PTFs) with a non port
900 defined and with 
PQ61462 applied (which resolves the issue
of the Nanny service failed to start using a non-900 port
numberand has no relevance in this situation) now has in the
nanny.trace file naming exceptions and warnings.
.
Cause:
This is due to the fact that the Nanny is waiting for the Admin
server to startup in the NameServices.
.
Example:
[6/6/02 10:20:50:012 CDT] 651afb75 Nanny         W SMTL0012W:
Waiting for initial context javax.naming.CommunicationException:
Caught CORBA.COMM_FAILURE when resolving initial
reference=WsnNameService.  Root exception is
org.omg.CORBA.COMM_FAILURE:   minor code: 3  completed: No
 at
com.ibm.CORBA.iiop.HTTPConnection.send(HTTPConnection.java:447)
 at
com.ibm.CORBA.iiop.ClientRequestImpl.invoke(ClientRequestImpl.ja
va:508)
 at
com.ibm.CORBA.iiop.ClientRequestImpl.reInvoke(ClientRequestImpl.
java:741)
 at
com.ibm.CORBA.iiop.ClientRequestImpl.reInvoke(ClientRequestImpl.
java:863)
 at
com.ibm.CORBA.iiop.ClientDelegate.invoke(ClientDelegate.java:894
)
 at
com.ibm.CORBA.iiop.InitialNamingClient.resolve(InitialNamingClie
nt.java:386)
 at
com.ibm.CORBA.iiop.InitialNamingClient.cachedInitialReferences(I
nitialNamingClient.java:591)
 at
com.ibm.CORBA.iiop.InitialNamingClient.resolve_initial_reference
s(InitialNamingClient.java:355)
 at
com.ibm.CORBA.iiop.ORB.resolve_initial_references(ORB.java:1816)
 at
com.ibm.ws.naming.util.WsnInitCtxFactory.mergeWsnNSProperties(Ws
nInitCtxFactory.java:590)
 at
com.ibm.ws.naming.util.WsnInitCtxFactory.getRootJndiContext(WsnI
nitCtxFactory.java:352)
 at
com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextIntern
al(WsnInitCtxFactory.java:227)
 at
com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:98)
 at com.ibm.ws.naming.util.WsnInitCtx.<init>(WsnInitCtx.java:79)
 at
com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContext(WsnIn
itCtxFactory.java:135)
 at
com.ibm.websphere.naming.WsnInitialContextFactory.getInitialCont
ext(WsnInitialContextFactory.java:80)
 at
javax.naming.spi.NamingManager.getInitialContext(NamingManager.j
ava:674)
 at
javax.naming.InitialContext.getDefaultInitCtx(InitialContext.jav
a:255)
 at javax.naming.InitialContext.init(InitialContext.java:231)
 at javax.naming.InitialContext.<init>(InitialContext.java:207)
 at
com.ibm.ejs.sm.util.process.Nanny.getInitialContext(Nanny.java:4
49)
 at
com.ibm.ejs.sm.util.process.Nanny.GetAdminNode(Nanny.java:475)
 at
com.ibm.ejs.sm.util.process.Nanny.AdminServerStartup(Nanny.java:
561)
 at com.ibm.ejs.sm.util.process.Nanny.main(Nanny.java:655)
 at java.lang.reflect.Method.invoke(Native Method)
 at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:158)
----- Begin backtrace for rootCause
org.omg.CORBA.COMM_FAILURE:   minor code: 3  completed: No
 at
com.ibm.CORBA.iiop.HTTPConnection.send(HTTPConnection.java:447)
 at
com.ibm.CORBA.iiop.ClientRequestImpl.invoke(ClientRequestImpl.ja
va:508)
 at
com.ibm.CORBA.iiop.ClientRequestImpl.reInvoke(ClientRequestImpl.
java:741)
 at
com.ibm.CORBA.iiop.ClientRequestImpl.reInvoke(ClientRequestImpl.
java:863)
 at
com.ibm.CORBA.iiop.ClientDelegate.invoke(ClientDelegate.java:894
)
 at
com.ibm.CORBA.iiop.InitialNamingClient.resolve(InitialNamingClie
nt.java:386)
 at
com.ibm.CORBA.iiop.InitialNamingClient.cachedInitialReferences(I
nitialNamingClient.java:591)
 at
com.ibm.CORBA.iiop.InitialNamingClient.resolve_initial_reference
s(InitialNamingClient.java:355)
 at
com.ibm.CORBA.iiop.ORB.resolve_initial_references(ORB.java:1816)
 at
com.ibm.ws.naming.util.WsnInitCtxFactory.mergeWsnNSProperties(Ws
nInitCtxFactory.java:590)
 at
com.ibm.ws.naming.util.WsnInitCtxFactory.getRootJndiContext(WsnI
nitCtxFactory.java:352)
 at
com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextIntern
al(WsnInitCtxFactory.java:227)
 at
com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:98)
 at com.ibm.ws.naming.util.WsnInitCtx.<init>(WsnInitCtx.java:79)
 at
com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContext(WsnIn
itCtxFactory.java:135)
 at
com.ibm.websphere.naming.WsnInitialContextFactory.getInitialCont
ext(WsnInitialContextFactory.java:80)
 at
javax.naming.spi.NamingManager.getInitialContext(NamingManager.j
ava:674)
 at
javax.naming.InitialContext.getDefaultInitCtx(InitialContext.jav
a:255)
 at javax.naming.InitialContext.init(InitialContext.java:231)
 at javax.naming.InitialContext.<init>(InitialContext.java:207)
 at
com.ibm.ejs.sm.util.process.Nanny.getInitialContext(Nanny.java:4
49)
 at
com.ibm.ejs.sm.util.process.Nanny.GetAdminNode(Nanny.java:475)
 at
com.ibm.ejs.sm.util.process.Nanny.AdminServerStartup(Nanny.java:
561)
 at com.ibm.ejs.sm.util.process.Nanny.main(Nanny.java:655)
 at java.lang.reflect.Method.invoke(Native Method)
 at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:158)
.
Request:
To have the warning message stack not appear in the nanny.trace
so when stacks are seen, they are known to be valid error
messages that need to be responded to by the administrator of
the system.
Local fix
No workaround available. Ignoring these errors is not sufficient
to the customer's needs.
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users running   *
*                 on Unix platforms.                           *
****************************************************************
* PROBLEM DESCRIPTION: Naming Exceptions are thrown when       *
*                      Nanny is waiting for AdminServer to     *
*                      start the Name Services.                *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Naming Exceptions are thrown when Nanny is waiting for the
AdminServer to start the Name Services.  These exceptions are
harmless, and can be ignored.
Problem conclusion
This fix provides a customizable startupTime (in millisecs)
property to be added in admin.config as follows:
com.ibm.ejs.sm.adminServer.startupTime=150000
Temporary fix Comments
APAR information
APAR number PQ62188
Reported component name WEBSPHERE AE AI
Reported component ID 5630A2200
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2002-06-12
Closed date 2002-07-17
Last modified date 2002-11-06

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
ADMINSVR          

SRLS

Fix information
Fixed component name WEBSPHERE AE AI
Fixed component ID 5630A2200

Applicable component levels
R400 PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ62188
IBM Group: Software Group
Modified date: Nov 6, 2002