7.16 Notes on restarting JP1/AO services
When you restart the JP1/AO service, some tasks might fail depending on the status of the task when the service was stopped. The following table describes the behavior of tasks when the JP1/AO service restarts:
No. |
Task status when JP1/AO service stops |
Task behavior when JP1/AO service restarts |
|
---|---|---|---|
Default behavior |
behavior when true is specified for task.execute.skip.serverStart in the user-specified properties file (config_user.properties). |
||
1 |
Waiting |
|
|
2 |
Suspended |
The task remains in Suspended status. |
|
3 |
In Progress |
The task enters Failed status. |
The task enters Failed status. |
4 |
Waiting for Input |
The task enters Failed status. |
The task enters Failed status. |
5 |
In Progress (with Error) |
The task enters Failed status. |
The task enters Failed status. |
6 |
In Progress (Terminating) |
The task enters Failed status. |
The task enters Failed status. |
7 |
Long Running |
The task enters Failed status. |
The task enters Failed status. |
8 |
Completed |
The task remains in Completed status. |
The task remains in Completed status. |
9 |
Failed |
The task remains in Failed status. |
The task remains in Failed status. |
10 |
Canceled |
The task remains in Canceled status. |
The task remains in Canceled status. |
- #1
-
For a recurring task, the task to be executed next is generated in the Waiting status.