WildFly Threads Subsystem Configuration: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
No edit summary
No edit summary
Line 52: Line 52:


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.
=Configure the Thread Pool on the Target Component=
For an example of how to configure the thread pool on a JBossWeb connector, see:
[[JBossWeb WildFly Subsystem Configuration#Thread_Pool_Configuration|JBossWeb Connector Thread Pool Configuration]]

Revision as of 21:39, 8 June 2016

External

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-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-factory"/>
    </unbounded-queue-thread-pool>
</subsystem>

where

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:

JBossWeb Connector Thread Pool Configuration