
|
If you were logged in you would be able to see more operations.
|
|
|
|
in case of a stateful job, there is no need to update trigger state from 'STATE_BLOCKED' to 'SATTE_WAINTING' if the trigger won't fire again.
The code that has to be changed is the following :
- method triggeredJobComplete, class JobStoreSupport :
if (jobDetail.isStateful()) {
getDelegate().updateTriggerStatesForJobFromOtherState(conn,
jobDetail.getName(), jobDetail.getGroup(),
STATE_WAITING, STATE_BLOCKED);
.....
}
must be replaced by the code :
if (jobDetail.isStateful()) {
String newState = STATE_COMPLETE;
if (trigger.getNextFireTime() != null) {
newState = STATE_WAITING;
}
getDelegate().updateTriggerStatesForJobFromOtherState(conn,
jobDetail.getName(), jobDetail.getGroup(),
newState, STATE_BLOCKED);
}
regards.
|
|
Description
|
in case of a stateful job, there is no need to update trigger state from 'STATE_BLOCKED' to 'SATTE_WAINTING' if the trigger won't fire again.
The code that has to be changed is the following :
- method triggeredJobComplete, class JobStoreSupport :
if (jobDetail.isStateful()) {
getDelegate().updateTriggerStatesForJobFromOtherState(conn,
jobDetail.getName(), jobDetail.getGroup(),
STATE_WAITING, STATE_BLOCKED);
.....
}
must be replaced by the code :
if (jobDetail.isStateful()) {
String newState = STATE_COMPLETE;
if (trigger.getNextFireTime() != null) {
newState = STATE_WAITING;
}
getDelegate().updateTriggerStatesForJobFromOtherState(conn,
jobDetail.getName(), jobDetail.getGroup(),
newState, STATE_BLOCKED);
}
regards. |
Show » |
|
Yes, but if the trigger won't fire again, it would have been taken care of in the preceding block of code. Thus only those triggers that are still "blocked" get set to "waiting".