|
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
- 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?
- 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 (available in V6.0 only)?
- 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 (available in V6.0 only)?
- 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 |
|
- Enable tracing:
- For V6.0 and V6.1:
- In the Administrative Console, expand Troubleshooting and
select Logs and Trace.
- In the Logging and Tracing page, select your server and then
Diagnostic Trace.
- Ensure that Enable Log is selected.
- Under Trace Output, select File, and accept the
defaults.
- 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 |
|
Note: The preceding trace string should be entered
as 1 line, with no spaces. |
|
- Click OK and save your configuration.
- Restart the application server.
- Reproduce the problem.
- Send the resulting trace output file.
- For V5.0 and V5.1:
- In the Administrative Console, expand Troubleshooting and
select Logs and Trace.
- In the Logging and Tracing page, select your server and then
Diagnostic Trace.
- Ensure that Enable trace with the following specification is
selected.
- 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. |
|
- Under Trace Output, select File, and accept the
defaults.
- Click OK and save your configuration.
- Restart the application server.
- Reproduce the problem.
- Send the resulting trace output file.
- 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 or
the WebSphere
Business Integration Server Foundation support site. |
|
|
|
|
|
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 |
|
|
|
|
|
|