You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 20, 2020. It is now read-only.
Jobs are submitted to a pool of threads.
Stopping a thread in Java is not the easiest thing to do 😄
It should be possible through the admin interface to stop an execution.
The server should keep track of the execution's Future objects and call cancel on the requested one.
This will set the interrupted flag on the execution thread which should be detected by the user's job using Thread.currentThread().isInterrupted(). This is possible out of the box if the job is an Easy Batch job.
The text was updated successfully, but these errors were encountered:
Jobs are submitted to a pool of threads.
Stopping a thread in Java is not the easiest thing to do 😄
It should be possible through the admin interface to stop an execution.
The server should keep track of the execution's
Future
objects and callcancel
on the requested one.This will set the
interrupted
flag on the execution thread which should be detected by the user's job usingThread.currentThread().isInterrupted()
. This is possible out of the box if the job is an Easy Batch job.The text was updated successfully, but these errors were encountered: