[
https://issues.jboss.org/browse/WFLY-11139?page=com.atlassian.jira.plugin...
]
Cheng Fang updated WFLY-11139:
------------------------------
Description:
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.
was:
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.
Exception from getRunningExecutions method causes undeployment to
hang
----------------------------------------------------------------------
Key: WFLY-11139
URL:
https://issues.jboss.org/browse/WFLY-11139
Project: WildFly
Issue Type: Bug
Components: Batch
Affects Versions: 14.0.0.Final
Reporter: Cheng Fang
Assignee: Cheng Fang
Priority: Major
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.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)