[jboss-jira] [JBoss JIRA] (WFLY-4478) Server won't shutdown until batch threads are done executing

Cheng Fang (JIRA) issues at jboss.org
Sat Apr 4 09:29:18 EDT 2015


    [ https://issues.jboss.org/browse/WFLY-4478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13056050#comment-13056050 ] 

Cheng Fang commented on WFLY-4478:
----------------------------------

Calling JobOperator.stop(jobExecutionId) should be able to stop the running job execution, though it's a request to stop.  JBeret calls the batchlet's stop() method to stop the batchlet, and a properly implemented batchlet should stop there; or stops the chunk stop execution as soon as the current chunk ends.

> Server won't shutdown until batch threads are done executing
> ------------------------------------------------------------
>
>                 Key: WFLY-4478
>                 URL: https://issues.jboss.org/browse/WFLY-4478
>             Project: WildFly
>          Issue Type: Bug
>          Components: Batch
>            Reporter: James Perkins
>            Assignee: James Perkins
>
> When the server is shutdown, even with {{SIGINT}}, the batch jobs keep running and the JVM will not exit until the batch jobs are complete. Ideally threads spawned from the {{BatchEnvironment}} will be daemon threads. At the least the thread should be interrupted.
> Another option would be for JBeret to have a way to stop all running jobs. 



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)


More information about the jboss-jira mailing list