The scheduler uses read-committed transaction isolation, by default,
when reading tasks using the get or find APIs on the com.ibm.websphere.scheduler.Scheduler
interface and WASScheduler MBean. The default behavior for a scheduler can
be changed to read-uncommitted, which allows the get and find methods to return
the current or next state of the task in the database. This topic describes
how to change the default behavior for the get and find methods.
About this task
See the scheduler
API documentation to view the com.ibm.websphere.scheduler.TaskInfo.setTaskExecutionOptions()
method, which details how to return the next state of the task or the current
state of the task.
Note: If the scheduler database does not support uncommitted
reads, such as Oracle, this parameter has no effect.
To change
the default behavior for the get and find methods, complete the following
steps:
Procedure
- From the administrative console, click Resources > Schedulers > scheduler_name.
- Click Custom Properties.
- Click New.
- Add the following properties:
Name |
defaultReadTransactionIso |
Type |
java.lang.Integer |
Value |
1 (for read-uncommitted transaction isolation)
2 (for read-committed transaction isolation)
|
- Click Apply or
- Click OK.
- Save the changes and
verify that you initiate a file synchronization before restarting the servers.
- Restart the application server for the changes to take effect.