![[AIX Solaris HP-UX Linux Windows]](../images/dist.gif)
![[IBM i]](../images/iseries.gif)
Command-line tool problems
Troubleshoot a variety of problems relating to using command-line tools.
The addNode.sh script or BBOWADDN job fails during node federation.
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.
With Windows service, there is no indication when a server is already started.
Using one or more % characters as part of the value for a parameter
- The "ADMU0125E: Change the clock of the new node to be within {0} minutes of the clock of the deployment manager" error message occurs during federation
- The stopServer command fails to stop the server because the system cannot create a connector to an invalid hostname.
Entering passwords on the command line
![[AIX Solaris HP-UX Linux Windows]](../images/dist.gif)
![[IBM i]](../images/iseries.gif)
The addNode.sh script or BBOWADDN job fails during node federation.
This error occurs only if the BBODCFGW job is run on the deployment manager during customization. The BBODCFGW adds an unmanaged node with a Web server to the deployment manager, causing the node federation from a base server to fail.
To fix this problem, do not configure the BBODCFGW job on the deployment manager until all nodes are federated into the cell. Also, do not add any unmanaged nodes into the cell until all node are federated. A web server can be configured on a managed node without any problems.
![[AIX Solaris HP-UX Linux Windows]](../images/dist.gif)
![[IBM i]](../images/iseries.gif)
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
![[AIX Solaris HP-UX Linux Windows]](../images/dist.gif)
![[IBM i]](../images/iseries.gif)
The startServer.sh or stopServer.sh commands fail to start or stop the server when the server definition is part of the configuration repository
startServer.sh webserver1 -nowait
stopServer.sh webserver1 -nowait
![[IBM i]](../images/iseries.gif)
![[Windows]](../images/windows.gif)
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.
![[Windows]](../images/windows.gif)
Using one or more % characters as part of the value for a parameter
- Invoking a command or .bat file, such as stopServer.bat from the profile_root directory, and the command or .bat file contains a call to a .bat file in the installation_root directory and
- Using one or more % characters as part of the value for a parameter
You must use two % characters (%%) for each % character contained in the parameter value to prevent the % characters that are part of the parameter value from being consumed by the operating system.
For example, if you want to use was%admin as the value of the-password parameter, you must specify the following command:
wsadmin.bat -username wsadmin -password was%%admin
instead of:
wsadmin.bat -username wsadmin -password was%admin
ADMU0125E: Change the clock of the new node to be within {0} minutes of the clock of the deployment manager
The workaround for this problem is to adjust the time on the node to be within the recommended amount of the deployment manager. Verify that the time zones are correct and that the times within the time zones are correct. For AIX systems, if the time on the node system is within five minutes of the deployment manager, review the timezone setting in the /etc/environment file. Verify that the TZ= property is set correctly. For example, in the Central Time Zone, it should read TZ=CST6CDT. For more information, see the environment file section of the Files Reference website.
stopServer command fails to stop the server because the system cannot create a connector to an invalid hostname
- 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.
- Issue the following command to connect to the
server:
wsadmin -host host_name -port connector_port -conntype [SOAP | RMI ] -user user_ID -password password
- 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")
- Issue the following command to connect to the
server:
![[Windows]](../images/windows.gif)
![[AIX]](../images/aixlogo.gif)
Entering passwords on the command line
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"
![[Windows]](../images/windows.gif)
stopserver server1 -username fn_wasadmin -password mypass35 -trace
![[AIX]](../images/aixlogo.gif)
stopserver server1 -username fn_wasadmin -password 'mypass35' -trace

- For a string containing a single quote or a double quote, use the other character to quote the
string. For example, if you specify bin/ws_ant.sh -f ant.xml -Dsystem.property='"a quoted
String"', the property is set to "a quoted string". Similarly, if
you specify bin/ws_ant.sh -f ant.xml -Dsystem.peoperty="'a quoted string'", the
property is set to 'a quoted string'.
You cannot include both single and double quotes in the same string.
- For a string containing a back quote, use a single quotes surrounding the string and escape the back quote with backslash. For example, if you specify bin/ws_ant.sh -f ant.xml -Dsystem.property='\`a quoted string\`', the property is set to `a quoted string`.
- For a string containing a backslash, surround the string with single quotes and escape it with a backslash. For example, if you specify bin/ws_ant.sh -f ant.xml -Dsystem.property='c:\\Program Files\\IBM'. the property is set to c:\Program Files\IBM.
- For a string containing a dollar sign, surround the string with single quotes and escape it with a backslash. For example, if you specify bin/ws_ant.sh -f ant.xml -Dsystem.property='\$3.99', the property is set to $3.99.
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.