Details
-
Bug
-
Resolution: Done
-
Critical
-
7.0.0.ER3
-
None
Description
Currently, batch subsystem seems to know nothing about graceful shutdown and suspending the server.
When doing a graceful shutdown (with a timeout), the timeout is ignored and the shutdown waits until all running batch jobs are finished. Other components of the application server proceed to shut down properly, so if a batch job uses, for example, a container-managed PersistenceContext, the job will then fail after persistence services are no longer available.
When the server is in suspended state, no new batch jobs should be accepted to run.
Attachments
Issue Links
- is blocked by
-
WFLY-4478 Server won't shutdown until batch threads are done executing
- Closed
- is related to
-
JBEAP-2785 Can't set the restart-on-resume property of Batch subsystem
- Closed
- relates to
-
WFLY-3769 Implement graceful shutdown for batch tasks
- Closed