Server1 fails to start in a stand-alone environment
 Technote (troubleshooting)
 
Problem(Abstract)
Scenario:
In a stand-alone environment, an attempt to start server1 fails.

Problem Determination Steps:

1. SystemOut.log shows no errors being written.

2. startServer.log shows that server 1 could not be initialized, did not create a process ID, and shows the system generates a permission denied entry as follows:

[6/30/04 19:20:31:222 CST] 15df3c9c UnixProcessIm > create() : Calling for a process create.
[6/30/04 19:20:31:222 CST] 15df3c9c UnixProcessIm d Creation params are: [executable:] /usr/WebSphere/AppServer/java/lib/fmcojagt.jar [command line args:] -Xmx256m -Dwas.status.socket=32828 -Xms50m -Xbootclasspath/p:/usr/WebSphere/AppServer/java/jre/lib/ext/ibmorb.jar:/usr/WebSphere/AppServer/java/jre/lib/ext/ibmext.jar -classpath /usr/WebSphere/AppServer/properties:/usr/WebSphere/AppServer/properties:/usr/WebSphere/AppServer/lib/bootstrap.jar:/usr/WebSphere/AppServer/lib/j2ee.jar:/usr/WebSphere/AppServer/lib/lmproxy.jar:/usr/WebSphere/AppServer/java/bin/java/fmcojagt.jar -Xmx256m -Dws.ext.dirs=/usr/WebSphere/AppServer/java/lib:/usr/WebSphere/AppServer/classes:/usr/WebSphere/AppServer/classes:/usr/WebSphere/AppServer/lib:/usr/WebSphere/AppServer/lib/ext:/usr/WebSphere/AppServer/web/help:/usr/WebSphere/AppServer/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime -Dserver.root=/usr/WebSphere/AppServer -Ddb2j.system.home=/usr/WebSphere/AppServer/cloudscapeCommon -Duser.install.root=/usr/WebSphere/AppServer -Dcom.ibm.itp.location=/usr/WebSphere/AppServer/bin -Dwas.install.root=/usr/WebSphere/AppServer -Djava.security.auth.login.config=/usr/WebSphere/AppServer/properties/wsjaas.conf -Djava.security.policy=/usr/WebSphere/AppServer/properties/server.policy com.ibm.ws.bootstrap.WSLauncher com.ibm.ws.runtime.WsServer /usr/WebSphere/AppServer/config mq02 mq02 server1 [environment:] EXTSHM=ON [working directory:] /usr/WebSphere/AppServer [umask:] 22 [Standard out/err filenames:] null /usr/WebSphere/AppServer/logs/server1/native_stdout.log /usr/WebSphere/AppServer/logs/server1/native_stderr.log [priority:] 20 [process group:] 0 [process name:] server1 [inheritParentStreams:] false[detachProcess:] false
[6/30/04 19:20:31:350 CST] 15df3c9c WsServerLaunc E ADMU3002E: Exception attempting to process server server1
[6/30/04 19:20:31:351 CST] 15df3c9c WsServerLaunc E ADMU3007E: Exception com.ibm.ws.process.exception.InvalidExecutableException: Error creating new process. 013: Permission denied
at com.ibm.ws.process.UnixProcessGlue.create(Native Method)
at com.ibm.ws.process.UnixProcessImpl.create(UnixProcessImpl.java:81)
at com.ibm.ws.process.ProcessFactory.create(Unknown Source)
at com.ibm.ws.management.launcher.ProcessLauncher.launch(ProcessLauncher.java:66)
at com.ibm.ws.management.launcher.LaunchCommand.launchProcess(LaunchCommand.java:162)
at com.ibm.ws.management.tools.WsServerLauncher.runTool(WsServerLauncher.java:193)
at com.ibm.ws.management.tools.AdminTool.executeUtility(AdminTool.java:173)
at com.ibm.ws.management.tools.WsServerLauncher.main(WsServerLauncher.java:91)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
 
Cause
The executableName value is incorrect.
[6/30/04 19:20:31:212 CST] 15df3c9c ProcessLaunch d Process CreationParams: [executable:] /usr/WebSphere/AppServer/java/lib/fmcojagt.jar
 
Resolving the problem
Things to check:
  1. Ensure that server1 has the correct privileges to run as a process.
  2. If you are running as a non-root user, verify that the logs directory has write permissions.
  3. 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.

 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > System Management/Repository
Operating system(s): AIX
Software version: 6.0
Software edition:
Reference #: 1173449
IBM Group: Software Group
Modified date: Aug 16, 2004