Opened 10 years ago
Closed 10 years ago
#1938 closed enhancement (fixed)
Force job status to ERROR
| Reported by: | Nicklas Nordborg | Owned by: | everyone |
|---|---|---|---|
| Priority: | major | Milestone: | BASE 3.5 |
| Component: | web | Version: | |
| Keywords: | Cc: |
Description
In some cases a job crashes without updating the status in BASE. For example, I had a recent crash of the database and everything just freezed and Tomcat and the database had to be restarted. The running jobs were left in EXECUTING state. The "Abort" button could be used to put the jobs in ABORTING state but since they were not actually running they never reached the final ERROR state.
There is also this case: http://baseplugins.thep.lu.se/ticket/758
It would be nice to be able to forcibly set the status of a job to ERROR.
Note:
See TracTickets
for help on using tickets.
(In [6856]) Fixes #1938: Force job status to ERROR
Added "Force error" button to the jobs view dialog. The button is visible for running jobs. For plug-ins that support the "Abort" functionality (which most should) the "Abort" button must be used before the "Force error" button is shown.