WildFly Threads Subsystem Concepts: Difference between revisions
Jump to navigation
Jump to search
| Line 5: | Line 5: | ||
=Executor Model= | =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 [[#How_Does_it_Relate_to_JBossWeb.3F|JBoss Web connectors]] | 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 [[#How_Does_it_Relate_to_JBossWeb.3F|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. | |||
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. | |||
=How Does it Relate to JBossWeb?= | =How Does it Relate to JBossWeb?= | ||
Revision as of 21:06, 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.
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.