Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer Scheduler service > Manage schedulers > Configure schedulers


Configure scheduler default transaction isolation

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.

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.

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...


Procedure

  1. From the administrative console, click Resources > Schedulers > scheduler_name.

  2. Click Custom Properties.

  3. Click New.

  4. Add the following properties:

    Name defaultReadTransactionIso
    Type java.lang.Integer
    Value 
    1 (for read-uncommitted transaction isolation)
2 (for read-committed transaction isolation)

  5. Click Apply or

  6. Click OK.

  7. Save the changes and verify that you initiate a file synchronization before restarting the servers.

  8. Restart the application server for the changes to take effect.


Configure schedulers


Related

+

Search Tips   |   Advanced Search