If you already contacted support, continue to the component-specific
MustGather information. Otherwise, click MustGather:
Read first for all WebSphere Application Server products.
Collecting Administrative scripting (wsadmin) specific MustGather
information
Use the following checklist to test and collect the correct information
to understand your wsadmin problems:
1. Do you receive the following error when attempting to start wsadmin?
WASX7023E: Error creating "SOAP"
connection to host "<name>"; |
 |
If yes:
- The server to which wsadmin is attempting to connect is not running.
- The port and hostname that wsadmin is attempting to use is incorrect.
- wsadmin is not supposed to connect to a running server and needs to
start with option, -conntype NONE.
|
|
2. If your wsadmin script (Java™ Command Language (JACL), JavaScript or
JPython) or a specific command fails to work:
- Determine the exact command that fails in your script or at the
command line.
- Enable tracing in wsadmin:
- Modify the wsadmin.properties file located in the following
directory:
- For V5.0 and V5.1:
- For V6.0 and V6.1:
install_root/profiles/profile_name/properties/ |
|
- Uncomment the following line by removing the "#":
com.ibm.ws.scripting.traceString=com.ibm.*=all=enabled |
|
- If wsadmin connects to a server process, enable tracing on that server
with the tracestring below. If you are unfamiliar with how to enable
server side tracing, see the instructions How
to setup a Trace?
- For V5.0 and V5.1:
- For V6.0 and V6.1
a. Recreate your problem by rerunning the script file.
b. Open a new Problem Management Record (PMR), if you have not already,
and forward the following files to the IBM Support Team:
- Run the collector tool against the profile and send in the
output .jar file. (instructions below)
- Script executed with the exact command used.
3. If wsadmin is hanging:
- Enable tracing in wsadmin:
- Modify the wsadmin.properties file in the following
directory:
- For V5.0 and V5.1:
- For V6.0 and V6.1:
install_root/profiles/profile_name/properties/ |
|
- Uncomment the following line by removing the #:
com.ibm.ws.scripting.traceString=com.ibm.*=all=enabled |
|
- If wsadmin connects to a server process, enable tracing on that
server. If you are unfamiliar with how to enable server side tracing, see
the instructions How
to setup a Trace?
- For V5.0 and V5.1:
- For V6.0 and V6.1:
- Recreate your problem.
- On UNIX platforms, when wsadmin hangs, execute three kill -3
pid commands, two minutes apart, on the wsadmin Process ID
(PID) and the server to which wsadmin connects.
- Run the collector tool against the profile and send in the
output JAR file. (instructions below)
- Send the javacore files created for AIX, Linux and
Windows.
- Note any issues on the machine and network during the hang.
4. Refer to the Information Center section entitled, Problems
starting or using the wsadmin command.
5. Open a PMR with IBM by performing one of the following:
6. Follow instructions to send
diagnostic information to IBM Support.
Gathering Data with the Collector Tool
What to do next
Once you have collected the preceding information, you can begin Analyzing
the data or simply submit
the diagnostic information to IBM support.
For a list of all technotes, downloads, and educational materials
specific to wsadmin, search the WebSphere
Application Server support site. |