MustGather: Application Server Startup Problems for All Releases of V3.5 and V4.0 Advanced Edition

Technote (FAQ)
Problem
MustGather for problems starting WebSphere® Application Server V3.5 and V4.0 System Management/Repository component. Gathering this information before calling IBM® support will help familiarize you with the troubleshooting process and save you time.
Solution
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

  1. Stop WebSphere Application Server, and purge all logs in the install_root/WebSphere/AppServer/logs directory
  2. 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.
  3. Start WebSphere Application using startupServer.sh script or the WebSphere Application Server Service in the Services window
  4. Load the administrative console
  5. Select the Application Server in the topology tree.
  6. Go to the Services tab, select Trace Service, and then Edit properties.
  7. 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.
  8. In the Trace Service window, specify also the "output file" with the fully qualified path. For example: C:\WebSphere\AppServer\logs\appservertrace.txt
  9. Click OK in the Trace Service window.
  10. Click Apply
  11. Start the Application Server, once the exception has occurred, note the time and date testing was performed and the exception thrown.
  12. Collect the following log files:
    tracefile, activity.log, nanny.trace, adminservertrace.txt , stderr, stdout, and appservertrace.txt
  13. Follow instructions to send diagnostic information to IBM support.

For a listing of all technotes, downloads, and educational materials specific to theSystem Management/Repository component, search the WebSphere Application Server support site

Related information
Submitting information to IBM support

Steps to getting support

MustGather: Readme first

Troubleshooting guide












Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, System Management/Repository
Operating system(s): AIX, HPUX, Linux, Multi-Platform, Solaris, Windows
Software version: 3.5, 4.0
Software edition: Advanced, Single Server, Standard
Reference #: 1141024
IBM Group: Software Group
Modified date: 2004-12-04