|
Problem |
MustGather for XMLConfig and client problems on WebSphere®
Application Server. 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.
XMLConfig and Client specific MustGather information
Collect the following documents for XMLConfig import or export issues.
XMLConfig is launched from
install_root/bin/XMLConfig.[sh|bat].
- If the failure occurs while running a script, run the individual
commands from the command prompt. If the commands fail, or if no script is
used, gather the following information:
- The exact command you used that fails, including all parameters that
were issued.
- Perform the following traces for more detailed information:
- Administrative Server Trace:
Edit the admin.config file of the WebSphere Application Server
server to which you are connecting with the XMLConfig client, clear out
existing logs, re-cycle administrative server:
Edit the install_root/bin/admin.config file and
uncomment the following two lines:
com.ibm.ejs.sm.adminServer.traceOutput=/path to WAS logs
directory/admin.trace
com.ibm.ejs.sm.adminServer.traceString=com.ibm.ejs.sm.*=all=enabled
- XMLConfig trace:
From the command line, process the import (all one line):
XMLConfig.sh/bat -import/export <xmlfile to import or
export> -adminNodeName <your node name> -traceString
"com.ibm.websphere.xmlconfig.*=all=enabled" -traceFile <absolute
path>\XML.trc
- The XMLConfig Client Process (Java™ virtual machine (JVM™)) hangs.
- Symptoms of a hang situation:
- XMLConfig Client is used for multiple or consecutive imports. This
might happen for wscp requests and from the console.
- A particular XMLConfig client JVM might work for a period of time
(N number of imports), then after the Nth import, the
XMLConfig client JVM does not respond to the import operation.
- At this point, open a new XMLConfig window (a new JVM); it will work
for a period of time also, then it too will hang as in the previous
symptom.
- The administrative server and application servers or clones continue
working.
- Since the XMLConfig JVM is in a hung state, you must gather the
following information:
- XMLConfig Client trace; issue the following example command:
XMLConfig.sh -import <xmlfile to import> -nodeName
<node name> -traceString
com.ibm.websphere.xmlconfig.*=all=enabled -traceFile
<absolute path>\XML.trc
- Issue a javacore from the XMLConfig Client JVM. Issue the following
command 3 times, each 60 seconds apart:
UNIX®: kill -3 <PID>
Windows®: Press Ctrl + Break from client window
- Provide the following additional documentation with the preceding
documents:
- install_root/logs/* (zip up
directory)
-
install_root/properties/com/ibm/product.xml
-
install_root/bin/admin.config
- If running a script, send in the script.
- Run a full XML export of the domain.
- Follow instructions to send
diagnostic information to IBM support.
For more information about XMLConfig script and client tool:
For a listing of all technotes, downloads, and educational materials
specific to the Administrative Scripting Tools component, search the WebSphere
Application Server support site. |
|
|