This topic provides troubleshooting support for a variety of problems relating to using command-line tools.
The just-in-time (JIT) compiler is disabled when you start the application server with Software Developer Kit (SDK) DEBUG enabled on a Red Hat Linux machine, even though JIT is set to enabled. To verify this setting, check the SystemOut.log or the startServer.log file.
Use the administrative console to remove the following DEBUG options of the Java process definition. -Xdebug -Xnoagent
startServer.sh webserver1 -nowait
stopServer.sh webserver1 -nowait
When attempting to start an already-started server from the command line, there is no indication that the server is already started and running. When running startManager.bat on Windows the following output is displayed before the command returns:
ADMU7701I: Because dmgr is registered to run as a Windows Service, the request to start this server will be completed by starting the associated Windows Service.
When running startServer.bat, the following output is displayed before the command returns:
ADMU7701I: Because server1 is registered to run as a Windows Service, the request to start this server will be completed by starting the associated Windows Service.
When running WASService.exe, the following output is displayed before the command returns:
Starting Service: service name
To check if the server is started or if the service is running, use the serverStatus server_name command or the WASService -status service_name command.
Or
wsadmin -host host_name -port connector_port -conntype [SOAP | RMI ] -user user_ID -password password
serverMBean = AdminControl.completeObjectName("*,type=Server") AdminControl.invoke(serverMBean, "stop")
There are operating system differences when specifying environment variables and for directory notation. When using the Windows command line, replace $variable with %variable% for environment variables and replace each forward slash (/) with a backslash (\) in directory paths. If you are using the bash shell on a Windows system, you can use the UNIX conventions.
On Unix type operating systems, it is usually better to always encapsulate string values associated with all tags in double quotes (""). You will also need to escape, using a '\' character, the following characters if they appear in the string values: '!', '\', '"', '`'. This will prevent some command line shells from interpreting specific characters within these values.
gsk7capicmd -keydb -create -db "/tmp/key.kdb" -pw "j\!jj"
stopserver server1 -username fn_wasadmin -password $mypass35%% -trace
stopserver server1 -username fn_wasadmin -password '$mypass35%' -trace
If none of these steps fixes your problem, check to see if the problem has been identified and documented by looking at the available online support (hints and tips, technotes, and fixes). If you don't find your problem listed there contact IBM support.