This article provides troubleshooting support for a variety of problems relating to using command line tools.
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 managed Node Federations are complete. A Web server can be configured on a managed node without any problems.
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.
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.
If you upgrade the deployment manager from V6.0.1 to V6.0.2, the server templates that are needed to create V5 servers are not available. This does not apply if you upgrade the deployment manager directly from V5.0, or V5.1, to V6.0.2.
Run the following command from the bin directory of the deployment manager profile to add the R5 server templates to your deployment manager profile and create V5 servers:
ws_ant.sh -buildfile updateNDProfileTemplates.xml
ws_ant.bat -buildfile updateNDProfileTemplates.xml
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 Web site.
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")
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.