If you have already contacted support, continue on to the
component-specific MustGather information. Otherwise, click: MustGather:
Read first for all WebSphere Application Server products.
Administrative server specific MustGather information
If you are experiencing problems starting the WebSphere administrative
server in a non-production environment, perform the following:
- Move all logs in the install_root/logs
directory to a new directory (for example, "oldlogs").
- 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.cm.*=all=enabled
com.ibm.ejs.sm.adminServer.traceOutput=\install_root\logs\adminservertrace.txt |
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.
|
- Start WebSphere using startupServer.sh script (UNIX®) or the
WebSphere Service in the Services Window. Once the exception has occurred,
note the time and date testing was performed and the exception thrown.
- Send in tracefile, activity.log, nanny.trace, and
adminservertrace.txt file.
- If you are experiencing problems starting the WebSphere administrative
server in a production environment, prefer to the following technote on
using DrAdmin to perform dynamic tracing. Trace the same traceString as
above:
How
to use DrAdmin with WebSphere Application Server V4.0
- Collect the files mentioned above.
- 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.
|