#1502 closed enhancement (fixed)
Add Signal.SHUTDOWN to plug-in signal system
| Reported by: | Nicklas Nordborg | Owned by: | Nicklas Nordborg |
|---|---|---|---|
| Priority: | minor | Milestone: | BASE 2.16 |
| Component: | core | Version: | |
| Keywords: | Cc: |
Description
The plug-in api has an elaborate signal system to let us send signals to plug-ins. Until now we have only defined Signal.ABORT which is used when the user clicks on the "Abort" button in the web interface. The same signal is used when the job agent/web server is shutting down which makes it impossible for a plug-in to know the source of the signal.
I suggest that a we define Signal.SHUTDOWN that is sent when the system is shutting down. In the future this would make it possible to develop plug-ins that survive a restart and continue working as if nothing has happened when the system is up and running again.
Of course, this will not work automatically, we need support at the job agent level so that it knows which jobs to re-start and at the plug-in level so that it knows were to begin.
Change History (4)
comment:1 by , 14 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:2 by , 14 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
(In [5399]) Fixes #1502: Add Signal.SHUTDOWN to plug-in signal system
The SHUTDOWN signal is now defined in the system and the job agent and internal job queue use this when shutting down (if supported by the plug-in, otherwise the ABORT signal is used).
No currently existing plug-ins support the SHUTDOWN signal and there is not support in the core or job agents to resume a job when the server starts up.