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. See the scheduler
Javadoc 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: