quickfix

Interface ExecutorFactory

public interface ExecutorFactory

Two Executors are required. The getLongLivedExecutor() is used for message processing and the getShortLivedExecutor() is used for timer tasks. They can both be the same underlying Executor if desired. Separating them allows for additional control such as with a ResourceAdapter WorkManager where the WorkManager differentiates between short and long lived Work.

By way of example, a single Executors.newCachedThreadPool() satisfies the requirements but really adds nothing over the default behavior.

Method Summary

Modifier and Type	Method and Description
Executor	getLongLivedExecutor() The message processing activities are long-lived so this Executor must have sufficient distinct Threads available to handle all your Sessions.
Executor	getShortLivedExecutor() The timer tasks are short-lived and only require one Thread (calls are serialized).

Method Detail

getLongLivedExecutor

Executor getLongLivedExecutor()

The message processing activities are long-lived so this Executor must have sufficient distinct Threads available to handle all your Sessions. The exact number will depend on how many concurrent Sessions you will have and whether you are using the Threaded or non-Threaded SocketAcceptors/Initiators.

getShortLivedExecutor

Executor getShortLivedExecutor()

The timer tasks are short-lived and only require one Thread (calls are serialized).