Technical data

Starting a WebLogic Managed Server
Administration Guide 2-19
Informational Thread Dumps When Starting Clusters
If a Managed Server is configured as follows, it prints an informational thread dump
to standard out during its startup cycle:
n Is a member of a cluster
n Prints messages of severity INFO and higher to standard out
(Specifed in the Administration Console on the Server > Logging > General
tab.)
n Logs remote exceptions
(Specified in the Administration Console on the Server > Logging > Debugging
tab.)
The thread dump is similar to the following abbreviated example:
Starting Cluster Service ....
<Nov 9, 2001 4:23:19 PM CST> <Info> <Connector> <Initializing J2EE
Connector Service>
<Nov 9, 2001 4:23:20 PM CST> <Info> <Dispatcher> <Exception thrown
by rmi server: 'weblogic.rmi.cluster.ReplicaAwareServerRef@9 -
jvmid:
'-5643957423891326779S:10.1.2.151:[7001,7001,7002,7002,7001,7002,
-1]:***specific server***', oid: '9', implementation:
'weblogic.jndi.internal.RootNamingNode@28c19b''
javax.naming.NameNotFoundException: Unable to resolve
weblogic.transaction.resources.Server01. Resolved:
'weblogic.transaction.resources' Unresolved:'Server01' ; remaining
name '' at
weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException
(BasicNamingNode.java:802)
at
weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode
.java:209)
at
weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNo
de.java:129)
.
.
.
If the Administration Server prints messages of INFO severity to standard out and logs
remote exceptions, it prints thread dumps while members of clusters are starting.