Things to check:
- Ensure that server1 has the correct privileges to run as a process.
- If you are running as a non-root user, verify that the logs directory
has write permissions.
- Verify the java executable name in server.xml file for server 1.
Example of an incorrect value in executableName field:
- <processDefinition xmi:type="processexec:JavaProcessDef"
xmi:id="JavaProcessDef_1" executableName="${JAVA_HOME}/lib/fmcojagt.jar"
workingDirectory="${USER_INSTALL_ROOT}" executableTargetKind="JAVA_CLASS" executableTarget="com.ibm.ws.runtime.WsServer">
<execution xmi:id="ProcessExecution_1" processPriority="20" runAsUser="" runAsGroup="" />
<ioRedirect xmi:id="OutputRedirect_1" stdoutFilename="${SERVER_LOG_ROOT}/native_stdout.log" stderrFilename="${SERVER_LOG_ROOT}/native_stderr.log"
/>
<monitoringPolicy xmi:id="MonitoringPolicy_1" maximumStartupAttempts="3" pingInterval="60" pingTimeout="300" autoRestart="true" nodeRestartState="STOPPED" />
- <jvmEntries xmi:id="JavaVirtualMachine_1" verboseModeClass="false" verboseModeGarbageCollection="false" verboseModeJNI="false" initialHeapSize="0"
maximumHeapSize="256" runHProf="false" debugMode="false" debugArgs="-Djava.compiler=NONE -Xdebug -Xnoagent
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=7777" disableJIT="false">
<classpath>${JAVA_HOME}/bin/java/fmcojagt.jar</classpath>
</jvmEntries>
</processDefinition>
In this example the executableName is set to a .jar file. Here is the
exact piece of the above for a clearer look:
executableName="${JAVA_HOME}/lib/fmcojagt.jar"
The exectuableName value should be set to the java directory. To correct
the problem, set it back to the default value:
executableName="${JAVA_HOME}/bin/java"
After this is changed and saved, you can start server1.
|