The JAVA_HOME variable in the variables.xml file should
not be changed. By default, the JAVA_HOME variable value is set to
Install_Root/java.
Here are the default tag entries in the variables.xml
file.
<entries xmi:id="VariableSubstitutionEntry_9"
symbolicName="JAVA_HOME"
value="/usr/WebSphere/AppServer/java"
description="The filesystem path to the Java Virtual Machine installation
directory."/>
If the value of the JAVA_HOME variable is changed , the DMGR or server1
fails to start.
Sample exception from Microsoft® Windows®
com.ibm.ws.process.exception.ProcessOpException: The system cannot
find the path specified.
003: No such process
at
com.ibm.ws.process.Win32ProcessImpl.create(Win32ProcessImpl.java:111)
at com.ibm.ws.process.ProcessFactory.create(Unknown Source)
at
com.ibm.ws.management.launcher.ProcessLauncher.launch(ProcessLauncher.ja
You can use the attached trace file to compare to the exception you
received.
Sample exception on AIX®
[8/5/04 16:04:43:358 CDT] 441b9b6a WsServer E WSVR0003E: Server dmgr
failed to start
com.ibm.ws.exception.ConfigurationError: Problem initializing
AdminImpl:
at
com.ibm.ws.management.component.AdminImpl.initialize(AdminImpl.java:413)
at
com.ibm.ws.runtime.component.ContainerImpl.initializeComponent(ContainerImpl.java:713)
You can use the attached trace file to compare to the exception you
received.
To check if JAVA_HOME has been changed:
- Edit
Install_Root/logs/servername/SystemOut.log file
and search for Java Home. You will see a line similar to the
following:
Java Home = /usr/WebSphere/AppServer/java/jre
- Start the server with the -trace option, for example,
./startserver.sh server1 -trace.
- Edit
Install_Root/logs/servername/startServer.log
Search for Xbootclasspath. You will see an entry similar to the
following:
-Xbootclasspath/p:/usr/WebSphere/AppServer/java/jre/lib/ext/ibmorb.jar;
|