Administration and administrative console troubleshooting tips
In WebSphere Application Server products, administrative functions are supported by:
- The appserver (such as server1) process in the base product
- The deployment manager (dmgr) process in the Network Deployment product
The process must be running to use the administrative console. The wsadmin command line utility has a local mode that you can use to perform administrative functions, even when the server process is not running.
When starting or stopping a server using a wsadmin interactive scripting session, you receive an exception indicating read timed out, for example:
WASX7015E: Exception running command: "$AdminControl startServer server1 Node1"; exception information: com.ibm.websphere.management.exception.ConnectorException org.apache.soap.SOAPException: [SOAPException: faultCode=SOAP-ENV:Client; msg=Read timed out; targetException=java.net.SocketTimeoutException: Read timed out]
This exception occurs because the timeout value is too small. To fix this, increase the timeout value specified by the com.ibm.SOAP.requestTimeout property in...
config_root/AppServer/properties/soap.client.props
...for a single server edition or in...
config_root/DeploymentManager/properties/soap.client.props
...for a network deployment installation. The value choose depends on a number of factors such as the size and the number of the applications installed on the server, the speed of your machine, and the level of usage of your machine. The default value of the com.ibm.SOAP.requestTimeout property is 180 seconds.
If you have problems starting or using the administrative console or wsadmin utility, verify that the supporting server process is started and that it is healthy.
- For the base product, look at these files:
- install_root/logs/server/startServer.log
For the message that indicates that the server started successfully: ADMU3000I: Server server1 open for e-business; process id is nnnn..
- install_root/logs/server/SystemOut.log
For the message that indicates that the server started successfully: WSVR0001I: Server server open for e-business.
- install_root/logs/server/startServer.log
- For the Network Deployment product, look at these files:
- install_root/logs/dmgr/startServer.log
For the message that indicates that the server started successfully: ADMU3000I: Server dmgr open for e-business; process id is nnnn..
- install_root/logs/dmgr/SystemOut.log
For this message indicating that the server started successfully: WSVR0001I: Server dmgr open for e-business.
- install_root/logs/dmgr/startServer.log
- For the z/OS product, check the job output.
- Look up any error messages in these files in the message reference table.
Select the Reference view in the information center navigation, then
click Messages.
- A message like WASX7213I: This scripting client is not connected to
a server process when trying to start wsadmin indicates that either the
server process is not running, the host machine where it is running is not
accessible, or that the port or server name used by wsadmin is incorrect.
- Verify that you are using the right port number to communicate with the
administrative console or wsadmin server using the following steps:
- Look in the SystemOut.log file.
- The line ADMC0013I: SOAP connector available at port nnnn indicates
the port that the server is using to listen for wsadmin functions.
- The property com.ibm.ws.scripting.port in the install_root/properties/wsadmin.properties file
controls the port used by wsadmin to send requests to the server. If it is
different from the value shown in the SystemOut.log file , either change the port number
in the wsadmin.properties file, or specify the correct port number
when starting wsadmin by using the -port port_number property
on the command line.
- The message SRVE0171I: Transport http is listening on port nnnn (default 9090) indicates the port the server uses to listen for administrative console requests. If it is different than the one specified in the URL for the administrative console, change the URL in the browser to the correct value. The default value is http://localhost:9090/admin.
- Look in the SystemOut.log file.
- Use the TCP/IP ping command to test that the hostname where the
appserver or deployment manager is executing, is reachable from the
system where the browser or wsadmin program are being used. If you are able
to ping the hostname, this indicates that there are no firewall or connectivity
issues.
- If the host where the appserver or deployment manager is running
is remote to the machine from which the client browser or wsadmin command
is running, ensure that the appropriate hostname parameter is correct:
- The hostname in the browser URL for the console.
- The -host hostname option of the wsadmin command that is used to direct wsadmin to the right server
- The hostname in the browser URL for the console.
- Tracing the administrative component:
WebSphere Application Server technical support might ask you to trace the administrative component for detailed problem determination. The trace specification for this component is...
com.ibm.websphere.management.*=all=enabled:com.ibm.ws.management.*=all=enabled"
If none of these steps solves the problem, see if the specific problem you are having is addressed in the Installation completes but the administrative console does not start topic. Check to see if the problem has been identified and documented using the links in the Diagnosing and fixing problems: Resources for learning topic. If you do not see a problem that resembles yours, or if the information provided does not solve your problem, contact IBM support for further assistance.
For current information available from IBM Support on known problems and their resolution, see the following topics on the IBM support page:
IBM Support has documents that can save you time gathering information needed to resolve this problem. Before opening a PMR, see the following topics on information gathering on the IBM support page:
Troubleshooting by task: What are you trying to do?
Troubleshooting installation problems