Command line tool problems

This article provides troubleshooting support for 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 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

For more information, see the V6.0 Information Center Release Notes page.

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

With Windows service, there is no indication when a server is already started. [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.

The 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 (e.g., on Unix based systems 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")

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.




Related tasks
Using command line tools
Reference topic    

Terms of Use | Feedback

Last updated: Oct 20, 2010 9:57:58 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-base-dist&topic=rtrb_commandprobs
File name: rtrb_commandprobs.html