WildFly Threads Subsystem Configuration: Difference between revisions
Jump to navigation
Jump to search
Line 43: | Line 43: | ||
</pre> | </pre> | ||
==unbounded-queue-thread-pool== | |||
==max-thread-count== | ===max-thread-count=== | ||
==keepalive-time time== | ===keepalive-time time=== | ||
==thread-factory== | ===thread-factory=== | ||
The <tt><thread-factory></tt> <tt>name</tt> should refer the thread factory previously defined. | The <tt><thread-factory></tt> <tt>name</tt> should refer the thread factory previously defined. |
Revision as of 21:59, 8 June 2016
External
- Define Thread Pools for HTTP Connectors https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html/Administration_and_Configuration_Guide/sect-Connector_Configuration.html#Define_Thread_Pools_for_HTTP_Connector_in_JBoss_Enterprise_Application_Platform
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
<subsystem xmlns="urn:jboss:domain:threads:1.1"> <thread-factory name="http-connector-thread-factory" thread-name-pattern="HTTP-%t" priority="9" group-name="http-threads"/> ... </subsystem>
where
name
thread-name-pattern
priority
group-name
Executor Configuration
<subsystem xmlns="urn:jboss:domain:threads:1.1"> ... <unbounded-queue-thread-pool name="http-thread-pool"> <max-threads count="500"/> <keepalive-time time="30" unit="seconds"/> <thread-factory name="http-connector-thread-factory"/> </unbounded-queue-thread-pool> </subsystem>
unbounded-queue-thread-pool
max-thread-count
keepalive-time time
thread-factory
The <thread-factory> name should refer the thread factory previously defined.
Configure the Thread Pool on the Target Component
For an example of how to configure the thread pool on a JBossWeb connector, see: