WildFly Threads Subsystem Concepts: Difference between revisions
Jump to navigation
Jump to search
| Line 10: | Line 10: | ||
An executor needs a ''thread factory'', that instantiates the threads required by the executor. The thread factory must be defined within the subsystem configuration and referred to from within the executor definition. | An executor needs a ''thread factory'', that instantiates the threads required by the executor. The thread factory must be defined within the subsystem configuration and referred to from within the executor definition. | ||
For details on how to configure an executor and its associated thread factory, see: | |||
<blockquote style="background-color: #f9f9f9; border: solid thin lightgrey;"> | |||
:[[WildFly Threads Subsystem Configuration]] | |||
</blockquote> | |||
=How Does it Relate to JBossWeb?= | =How Does it Relate to JBossWeb?= | ||
Revision as of 21:11, 8 June 2016
Internal
Executor Model
Thread pools defined by the "threads" subsystem can be shared between WildFly components that are compatible with the executor model. An example of such components are JBoss Web connectors.
An executor is an asynchronous execution mechanism capable of executing tasks in the background. The terms "executor" and "thread pool" are equivalent in this context and can be used interchangeably. Also see java.util.concurrent Executors.
An executor needs a thread factory, that instantiates the threads required by the executor. The thread factory must be defined within the subsystem configuration and referred to from within the executor definition.
For details on how to configure an executor and its associated thread factory, see: