Command-line tool problems

Troubleshoot a variety of problems relating to using command-line tools.

What kind of problem are you having?

Just-in-time (JIT) compiler is disabled when you start application server with DEBUG enabled on a Red Hat Linux machine
The startServer.sh or stopServer.sh commands fail to start or stop the server when the server definition is part of the configuration repository.
The stopServer command fails to stop the server because the system cannot create a connector to an invalid hostname.

Just-in-time (JIT) compiler is disabled when you start the application server with DEBUG enabled on a Red Hat Linux machine

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

Note: This topic references one or more of the application server log files. As a recommended alternative, you can configure the server to use the High Performance Extensible Logging (HPEL) log and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files on distributed and IBM® i systems. You can also use HPEL in conjunction with your native z/OS® logging facilities. If you are using HPEL, you can access all of your log and trace information using the LogViewer command-line tool from your server profile bin directory. See the information about using HPEL to troubleshoot applications for more information on using HPEL.

The startServer.sh or stopServer.sh commands fail to start or stop the server when the server definition is part of the configuration repository

This problem occurs when the startServer.sh or stopServer.sh commands are trying to start or stop non Java process. To solve this problem, use the -nowait option to start or stop the server, for example:

startServer.sh webserver1 -nowait

stopServer.sh webserver1 -nowait

No indication that a server is already started on Windows

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.

stopServer command fails to stop the server because the system cannot create a connector to an invalid hostname

If the stopServer command fails to stop the server because the system cannot create a connector to an invalid hostname, you can stop the server using one of following methods:

Stop the server process on the operating system (for example, on AIX, HP-UX, Linux, or Solaris computers, issue the kill command).
Or
Open a wsadmin tool connection directly to the connector port of the server and call the stop method for the MBean of the server. This method is recommended because it allows ongoing work to shut down gracefully.
1. Issue the following command to connect to the server:
```
wsadmin -host host_name  -port connector_port  -conntype [SOAP | RMI ] 
-user user_ID -password password
```
2. Invoke the stop method on the MBean of the server. For example, in Jython you can use:
```
serverMBean = AdminControl.completeObjectName("*,type=Server")
   AdminControl.invoke(serverMBean, "stop")
```

[IBM i] 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.