WildFly Threads Subsystem Configuration: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 5: | Line 5: | ||
=Overview= | =Overview= | ||
This page describes the steps required to define an executor and its associated thread factory. For a description behind the WildFly executor model, see [[WildFly Threads Subsystem Concepts#Executor_Model|WildFly Threads Subsystem Executor Model]]. | This page describes the steps required to define an executor and its associated thread factory. For a description behind the WildFly executor model, see [[WildFly Threads Subsystem Concepts#Executor_Model|WildFly Threads Subsystem Executor Model]]. The example below is fit to be used with a JBossWeb HTTP connector. | ||
=Thread Factory Configuration= | |||
=Executor Configuration= | |||
=Example= | =Example= | ||
Revision as of 21:12, 8 June 2016
Internal
Overview
This page describes the steps required to define an executor and its associated thread factory. For a description behind the WildFly executor model, see WildFly Threads Subsystem Executor Model. The example below is fit to be used with a JBossWeb HTTP connector.
Thread Factory Configuration
Executor Configuration
Example
<subsystem xmlns="urn:jboss:domain:threads:1.1">
<thread-factory name="http-connector-factory" group-name="example-thread-pool" thread-name-pattern="http-%t" priority="9"/>
<unbounded-queue-thread-pool name="uexample-thread-pool">
<max-threads count="500"/>
<keepalive-time time="30" unit="seconds"/>
<thread-factory name="http-connector-factory"/>
</unbounded-queue-thread-pool>
</subsystem>