MustGather: Scheduler problems for WebSphere Application Server V5.0 and V6.0 releases
 Technote (troubleshooting)
 
Problem(Abstract)
Collecting data for problems with the IBM® WebSphere® Application Server Scheduler component, a Programming Model Extension (PME) that is available in WebSphere Application Server V5.0 Enterprise Edition, WebSphere Business Integration Server Foundation V5.1, and all editions of WebSphere Application Server V6.0 and V6.1. Gathering this information before calling IBM support will help familiarize you with the troubleshooting process and save you time.
 
Resolving the problem
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.
Scheduler specific MustGather Information
  1. What is the exact version and the edition (for example: Base, Enterprise, WebSphere Business Integration Server Foundation, Network Deployment) of WebSphere Application Server that is installed?

  2. Provide a full description of the problem that you have encountered, including the stack traces of any errors or exceptions that are occurring. Provide any logs that contain the errors or exceptions.

  3. Under what circumstances does the problem occur? Does it occur every time a certain task is done or does it occur intermittently? Has this problem always occurred? If not, was a change recently made before the problem started to occur?

  4. What is the name and JNDI name of the Scheduler that you have configured?

  5. What is the name and JNDI name of the data source used by the Scheduler, and what database (including version) is used for the Scheduler tables? Also, what JDBC driver (and version) is used?

  6. Have the Scheduler tables been created? What is the output of the Verify tables button for the Scheduler in the Administrative Console (available in V6.0 only)?

  7. Is the problem occurring for EJB tasks or JMS tasks?

  8. Are the tasks scheduled by an application using the Scheduler API or from an administrative script using JMX (available in V6.0 only)?

  9. Send the SystemOut.log file for the application server on which the Scheduler problem occurs:
    • For V6.0 and V6.1, the standard output log is located in the following directory:

      install_root/profiles/profile_name/logs/server_name

    • For V5.0 and V5.1, the standard output log is located in the following directory:

      install_root/logs/server_name

  10. Enable tracing:
    • For V6.0 and V6.1:
      1. In the Administrative Console, expand Troubleshooting and select Logs and Trace.

      2. In the Logging and Tracing page, select your server and then Diagnostic Trace.

      3. Ensure that Enable Log is selected.

      4. Under Trace Output, select File, and accept the defaults.

      5. Click OK and save your configuration.

      6. Again expand Troubleshooting and select Logs and Trace.

      7. In the Logging and Tracing page, select your server and then Change Log Detail Levels.

      8. Enter the following trace string:

        *=info:Scheduler=all
        :ExtHelper=all
        :LeaseManager=all
        :AsynchBeans=all
        :AsynchBeans_Alarms=all
        :WAS.j2c=all:RRA=all

        Note: The preceding trace string should be entered as 1 line, with no spaces.

      9. Click OK and save your configuration.

      10. Restart the application server.

      11. Reproduce the problem.

      12. Send the resulting trace output file.

    • For V5.0 and V5.1:
      1. In the Administrative Console, expand Troubleshooting and select Logs and Trace.

      2. In the Logging and Tracing page, select your server and then Diagnostic Trace.

      3. Ensure that Enable trace with the following specification is selected.

      4. In the Trace Specification field, enter the following:

        Scheduler=all=enabled
        :ExtHelper=all=enabled
        :LeaseManager=all=enabled
        :AsynchBeans=all=enabled
        :AsynchBeans_Alarms=all=enabled
        :WAS.j2c=all=enabled
        :RRA=all=enabled

        Note: The preceding trace string should be entered as 1 line, with no spaces.

      5. Under Trace Output, select File, and accept the defaults.

      6. Click OK and save your configuration.

      7. Restart the application server.

      8. Reproduce the problem.

      9. Send the resulting trace output file.

  11. Run the collector tool to produce a JAR file containing your WebSphere configuration files and other logs that are useful to the WebSphere Application Server support team:
  12. Follow instructions to send the following diagnostic information to IBM support:
    • SystemOut.log
    • The trace output file
    • The collector output

For a listing of all technotes, downloads, and educational materials specific to the Scheduler component, search the WebSphere Application Server support site or the WebSphere Business Integration Server Foundation support site.
 
Related information
Submitting information to IBM support
Steps to getting support
MustGather: Read first
Troubleshooting guide
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers WebSphere Application Server Enterprise Scheduler AIX, HP-UX, Linux, Solaris, Windows 5.1, 5.0
Business Integration WebSphere Business Integration Server Foundation AIX, HP-UX, Linux, Solaris, Windows 5.1
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Programming Model Extensions (PME)
Operating system(s): Windows
Software version: 6.1
Software edition:
Reference #: 1220349
IBM Group: Software Group
Modified date: Nov 30, 2007