-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
14.0.0.Final
-
None
When undeploying a batch application, or stopping the server with active batch application deployment, the batch subsystem tries to get all running batch job executionsm, and to stop them before undeploying the application or shutting down the server.
When exceptions occurs from calling batchJobReposiotory.getRunningExecutions, the undeployment operation hangs. This happens to both in-memory and jdbc batch job repository. These exceptions may be caused by database server down, or connection timeout, for instance.
- is related to
-
JBEAP-15589 [GSS] (7.1.z) undeploy and shutdown hang by JdbcRepository error
- Closed
-
JBEAP-17944 [GSS] (7.2.z) undeploy and shutdown hang by JdbcRepository error
- Closed
- relates to
-
JBERET-458 getRunningExecutions() should look in cache as fallback
- Resolved