6.6.7. Multi-thread Execution Control Handler

This handler creates subthreads and parallelly executes the process of subsequent handlers on the handler queue on each subthread. The process result of this handler is an object (MultiStatus) with the aggregate of the execution results of each subthread.

This handler performs the following process.

The process flow is as follows.

../../../../_images/flow20.png Module list

</dependency> Specify the thread count

By default, this handler launches only one subsequent subthread and executes the handler.

If the performance can be improved by parallelizing the subsequent process (for example, batch action process), multiplexing of the subsequent handler processes can be done by changing the configuration value.

An example is shown below.

<component class = "nablarch.fw.handler.MultiThreadExecutionHandler">
  <!-- Execute the subsequent handler in 8 multiplexes -->
  <property name="concurrentNumber" value="8" />


If the processes after this handler are executed in multiple threads, make sure that the implementation of the subsequent handler or batch action is thread safe. Note that when a process that is not guaranteed to be thread safe is carelessly executed in multiple threads, unexpected exceptions may occur and may cause data inconsistency. Execute an arbitrary process before and after starting a thread

This handler performs a callback process before and after a subthread is activated.

The callback process is executed at the following three points.

  • Before starting the subthread
  • After the end of all threads following the exception that occurred in the subthread
  • After all subthreads have ended (will be executed even if an exception occurs in the subthread)

The process to be called back is the handler that implements ExecutionHandlerCallback among the handlers configured after this handler. If multiple handlers implement ExecutionHandlerCallback , then the callback process is performed sequentially from the handler that has been configured earlier.


Note that if multiple handlers have implemented the callback process and an error or exception occurs during the callback process, the callback process for the remaining handlers is not performed.


The database process performed in the callback process uses the database connection and transaction configured in the handler queue of the parent thread. Therefore, the update process performed in these processes is confirmed (commit) by the Transaction Control Handler configured in the parent thread after this handler ends.

When it is necessary to immediately confirm the process performed in the callback process, use the individual transaction instead of the database connection configured in the parent thread and perform the processing.

See below for details.

An implementation example of the callback process is shown below.

public class SampleHandler implements Handler<Object, Result>, ExecutionHandlerCallback<Object, Result> {

  public Result handle(Object input, ExecutionContext context) {
    // Implement handler process.
    return context.handleNext(input);

  public void preExecution(Object input, ExecutionContext context) {
    // Implement the callback process before the launch of the subthread

  public void errorInExecution(Throwable error, ExecutionContext context) {
    // Implement the callback process in the case of an error in the subthread

  public void postExecution(Result result, ExecutionContext context) {
    // Implement the callback process after the completion of the subthread
    // Whether the process of the subthread ended normally can be determined from the result of the argument.
    if (result.isSuccess()) {
        // Normal termination of subthread
    } else {
        // Abnormal termination of subthread
} Behavior when an exception occurs in a subthread

When an unexpected exception occurs in a subthread, call ThreadPoolExecutor#shutdownNow() for the abnormal termination of the batch application, safely end the processing of other subthreads that have not thrown an exception after data under process is completed.

When transaction management is done for each subthread by configuring Database Connection Management Handler and Transaction Control Handler on the subthread, operation of the parent thread and subthread when an exception occurs in the subthread is shown below.

  1. Suspension and roll back of the subthread in which the exception occurs.
  2. The parent thread closes the data reader being used by each subthread.
  3. The parent thread sends a stop request to all subthreads.
  4. Since the data reader of each subthread is already closed in 2. , the subthreads are normally terminated when the process under execution is completed.


If a InterruptedException exception is caught, it indicates that the process cannot be performed securely due to an interrupt request. In this case, the process is aborted by throwing an exception.