|
Problem |
MustGather for administrative console problems in releases
of WebSphere® Application Server V4.0. Gathering this information before
calling IBM® support helps familiarize you with the troubleshooting
process and saves you time. |
|
Solution |
If you have already contacted support, continue to the
component-specific MustGather information. Otherwise, click: MustGather:
Read first for all WebSphere Application Server products.
Administrative Console specific MustGather information
- For all release of V4.0 Advanced Edition:
- Verify if the console is local or remote.
- If the console is remote, verify that the remote console can be loaded
locally.
- If the console cannot be loaded locally, you will not be able to
connect remotely.
- If the console runs locally but not remotely, perform the following
before performing a trace:
- Can you resolve the hostname and IP address from the remote machine?
- If you use DNS to resolve server names, run the following command from
a command window:
nslookup hostname |
|
This command returns the following information: |
|
Server |
DNS Server Fully Qualified Domain Name (FQN) |
Address |
DNS Server IP Address |
Name |
Hostname Fully Qualified Domain Name |
Address |
Hostname IP Address |
|
|
- If the server is not registered or is misconfigured in DNS you get the
following response:
DNS Server cannot resolve the
hostname. |
|
Consult with your network administrator to ensure that
the hostname is resolved by DNS or host files. |
|
- If the preceding step is successful, verify that the client and server
are running the same version of WebSphere Application server and the same
Java™ SDK levels.
If the server is running V4.0.4, the client must also be at V4.0.4.
To verify that client and server are at the same JDK levels, perform the
following command in the install_root/java/bin
directory:
java -fullversion |
|
Both client and server should be running the same level
of the JDK. |
|
- After verifying steps 1 and 2, if the administrative console still
does not load, gather the following traces:
- Administrative server trace:
- Edit the install_root/bin/admin.config file
and uncomment the following two lines:
com.ibm.ejs.sm.adminServer.traceOutput=logs_dir/admin.trace
com.ibm.ejs.sm.adminServer.traceString=com.ibm.ejs.sm.*=all=enabled
|
|
- Save the admin.config file, then recycle the administrative
server.
- To ensure that logs are from the current test only, delete or backup
the /logs directory per your policies.
- Administrative client trace:
When running the adminclient run it in debug mode:
adminclient debug hostname >
adminclienttrace.txt 2>&1 |
|
Note: For UNIX® platforms, use a dollar sign (
$ ) instead of an ampersand ( & ).The 2>&1
or the 2>$1 means that the output of STDERR (file handle 2) is
redirected to the same place as STDOUT (file handle 1). So by issuing the
command >outputfile 2>&1, both the STDOUT and STDERR
output is redirected to the same file.
|
Note: If you modify the bootstrap port for the administrative
server from the default value of 900, you must also specify the port
number after the hostname in the preceding command.
Along with preceding generated logs to analyze the console problem, send
the entire logs from the install_root/logs
directory, product.xml file and admin.config file. |
|
- Follow instructions to send
diagnostic information to IBM support.
For a listing of all technotes, downloads, and educational materials
specific to the Administrative Console component, search the WebSphere
Application Server support site. |
|
|