Troubleshooting
Problem
Collecting data for problems with the IBM WebSphere Application Server Scheduler component, a Programming Model Extension (PME) that is available in 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. Gathering this information before calling IBM support will help familiarize you with the troubleshooting process and save you time.
- What is the exact version and the edition (for example: Base, Network Deployment) of WebSphere Application Server that is installed?
- 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.
- 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?
- What is the name and JNDI name of the Scheduler that you have configured?
- 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?
- Have the Scheduler tables been created? What is the output of the Verify tables button for the Scheduler in the Administrative Console?
- Is the problem occurring for EJB tasks or JMS tasks?
- Are the tasks scheduled by an application using the Scheduler API or from an administrative script using JMX?
- Send the SystemOut.log file for the application server on which the Scheduler problem occurs:
- The standard output log is located in the following directory:
install_root/profiles/profile_name/logs/server_name - Enable tracing:
- For WebSphere Application Server V7.0 and higher:
- In the Administrative Console, expand Troubleshooting and select Logs and Trace.
- In the Logging and Tracing page, select your server and then Diagnostic Trace.
- Under Trace Output, select File, and set the Maximum File Size to 50 and Maximum Number of Historical Files to 5.
- Set the Trace Output Format to Basic (Compatible).
- Click OK and save your configuration.
- Again expand Troubleshooting and select Logs and Trace.
- In the Logging and Tracing page, select your server and then Change Log Detail Levels.
- Enter the following trace string:
*=info:Scheduler=all:ExtHelper=all:LeaseManager=all:AsynchBeans=all:AsynchBeans_Alarms=all:WAS.j2c=all:RRA=all
- Click OK and save your configuration.
- Restart the application server.
- Reproduce the problem.
- Send the resulting trace output file(s).
- 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:
- 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 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 |
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:
- IBM Support Assistant (ISA)
- Service Request (SR)
- FTP to the Enhanced Customer Data Repository (ECuRep)
Related Information
[{"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Programming Model Extensions (PME)","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"9.0;8.5.5;8.0;7.0","Edition":"Base;Network Deployment","Line of Business":{"code":"LOB45","label":"Automation"}},{"Product":{"code":"SS2KS6","label":"WebSphere Business Integration Server Foundation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":" ","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"5.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}},{"Product":{"code":"SSNVBF","label":"Runtimes for Java Technology"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Java SDK","Platform":[{"code":"","label":""}],"Version":"","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]