If you have already contacted support, continue on to the
component's specific MustGather information. Otherwise, click on the
following link: MustGather:
Read First for all WebSphere Application Server Products.
System Management/Repository start specific MustGather
information
- Stop WebSphere Application Server, and purge all logs in the
install_root/WebSphere/AppServer/logs
directory
- Edit the admin.config file and add or modify the following
two lines:
com.ibm.ejs.sm.adminServer.traceString=com.ibm.ejs.sm.*=all=enabled
com.ibm.ejs.sm.adminServer.traceOutput=\install_root\logs\adminservertrace.txt
Note: The traceString will vary depending on start issue. You want to
trace the component that is throwing the exception listed at the top of
the stack.
- Start WebSphere Application using startupServer.sh script or
the WebSphere Application Server Service in the Services window
- Load the administrative console
- Select the Application Server in the topology tree.
- Go to the Services tab, select Trace Service, and then
Edit properties.
- In the Trace Service window, specify the trace string:
com.ibm.ejs.sm.*=all=enabled
Note: The traceString will vary depending on startup issue. You want
to trace the component that is throwing the exception listed at the top of
the stack.
- In the Trace Service window, specify also the "output file"
with the fully qualified path. For example:
C:\WebSphere\AppServer\logs\appservertrace.txt
- Click OK in the Trace Service window.
- Click Apply
- Start the Application Server, once the exception has occurred, note
the time and date testing was performed and the exception thrown.
- Collect the following log files:
tracefile, activity.log, nanny.trace, adminservertrace.txt , stderr,
stdout, and appservertrace.txt
- Follow instructions to send
diagnostic information to IBM support.
For a listing of all technotes, downloads, and educational materials
specific to the System Management/Repository component, search the WebSphere
Application Server support site
|