MustGather: Scheduler problems for WebSphere Application Server

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. Gathering this information before calling IBM support will help familiarize you with the troubleshooting process and save you time.

Resolving the problem

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. Gathering this information before calling IBM support will help familiarize you with the troubleshooting process and save you time.

To improve the accuracy of complete data collection, IBM recommends you use the automated data collectors within IBM Support Assistant. Not only will the automated collector gather the equivalent of the manual process, it will also provide a secure file transfer of the collection to IBM.

Collecting data using the IBM Support Assistant Data Collector

  1. Go to the ISA Data Collector site for WebSphere Application Server.

  2. Start the ISA Data Collector:
    • To run online, select the option to collect from this system using the current browser and click Start Collection.

    • To run locally, select the option to collect from this or another system using a downloadable utility. Download and extract the zip file to your WAS_HOME directory. From a command line, run isadc.[sh|bat] or launch index.html to use the web interface.

    • Beginning with WebSphere Application Server V8.0.0.6, the IBM Support Assistant Data Collector (ISADC) tool is bundled with the product. The ISADC tool is also provided for the WebSphere Application Server Liberty profile starting with V8.5.0.1.  As a result, you can run the ISADC tool directly from the app_server_root/bin directory. For more details, see Using the IBM Support Assistant Data Collector

  3. Select the Runtime > Scheduler Problem collector and click Start.

  4. Follow the prompts to automatically submit the collected data to IBM Support.

Collecting data manually

  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 and above)?

  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 and above)?

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

      install_root/profiles/profile_name/logs/server_name

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

      install_root/logs/server_name

  10. Enable tracing:
    • For WebSphere Application Server V6.0 and higher:
      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. Under Trace Output, select File, and set the Maximum File Size to 50 and Maximum Number of Historical Files to 5.

      4. Set the Trace Output Format to Basic (Compatible).

      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

      9. Click OK and save your configuration.

      10. Restart the application server.

      11. Reproduce the problem.

      12. Send the resulting trace output file(s).

    • For WebSphere Application Server 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

      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 for WebSphere Application Server
MustGather: Read first for WebSphere Application Server
Troubleshooting guide for WebSphere Application Server

Exchanging data with IBM Support

To diagnose or identify a problem, it is sometimes necessary to provide Technical Support with data and information from your system. In addition, Technical Support might also need to provide you with tools or utilities to be used in problem determination. You can submit files using one of following methods to help speed problem diagnosis:


Read first and related MustGathers


Cross reference information
Segment Product Component Platform Version Edition
Business Integration WebSphere Business Integration Server Foundation AIX, HP-UX, Linux, Solaris, Windows 5.1
Application Servers Runtimes for Java Technology Java SDK

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere Application Server
Programming Model Extensions (PME)

Software version:

5.1, 6.0, 6.1, 7.0, 8.0, 8.5

Operating system(s):

AIX, HP-UX, Linux, Solaris, Windows

Software edition:

Base, Enterprise, Network Deployment, WebSphere Business Integrations Server Foundation

Reference #:

1220349

Modified date:

2012-04-16

Translate my page

Machine Translation

Content navigation