Check the following to find the root cause.
- Start the server with -trace option.
- Review the startServer.log file and search for "Creation params are"
and make sure non of the expanded parameters are 'null' . In this case
Standard out/err filenames are null.
- Check the server.xml file and make sure fileName in
errorStreamRedirect and outputStreamRedirect contains valid variable or a
valid directory Structure. If not modify the file to contain the valid
directory structure.
- Make sure the variables are valid. Check the variables.xml file under
serverName and also under the nodeName . The variables should contain a
valid Name and Value. For example it should contain symbolicName and Value
as follows.
<entries xmi:id="VariableSubstitutionEntry_7" symbolicName="LOG_ROOT"
value="${USER_INSTALL_ROOT}/logs" description="The filesystem path to the
directory which will contain server log files."/>
In this case, value parameter itself was missing in the LOG_ROOT entry.
After adding the value parameter the server came up fine.
Location of the files :
server.xml -
install-root/config/cells/CellName/nodes/NodeName/servers/servername
Server Level variables.xml -
install-root/config/cells/CellName/nodes/NodeName/servers/servername
Node Level variables.xml -
install-root/config/cells/CellName/nodes/NodeName
Note : The same issue might happen on WAS 5.1also, but we may see the
failing variable or the file name in the startServer.log file.
|