Technical data

4 Configuring, Starting, and Stopping Node Manager
4-16 Configuring and Managing WebLogic Server
Node Manager and Managed Server States
Node Manager defines its own, internal Managed Server states for use when restarting
a server. If Node Manager is configured to restart Managed Servers, you may observe
these states in the Administration Console during the restart process.
! FAILED_RESTARTING—Indicates that Node Manager is currently restarting a
failed Managed Server.
Applications on the
ManagedServer are using
the wrong directory for
lookups.
Applications deployed to WebLogic Server should never make
assumptions about the current working directory. File lookups
should generally take place relative to the Root Directory
obtained with the
ServerMBean.getRootDirectory()
method (this defaults to the “.” directory). For example, to
perform a file lookup, use code similar to
String rootDir =
ServerMBean.getRootDirectory();
//application root directory
File f = new File(rootDir + File.separator +
"foo.in");
rather than simply:
File f = new File("foo.in");
If an application is deployed to a server that is started using
Node Manager, use the following method calls instead:
String rootDir //application root directory
if ((rootDir =
ServerMBean.getRootDirectory()) ==
null) rootDir =
ServerStartMBean.getRootDirectory();
File f = new File(rootDir + File.separator +
"foo.in");
The ServerStartMBean.getRootDirectory() method
obtains the Root Directory value that you specified when
configuring the server for startup using Node Manager. (This
corresponds to the Root Directory attribute specified the
Configuration->Remote Start page of the Administration
Console.)
Symptom Explanation