JBossWeb WildFly Subsystem Configuration

Internal

• JBossWeb WildFly Subsystem
• JBossWeb WildFly Subsystem Concepts

Schemas

JBoss Web standalone.xml configuration schema: docs/schema/jboss-as-web_*.xsd

AJP/HTTP Thread Number Configuration

Direct Connector Configuration

The maximum number of threads handling HTTP requests (over the HTTP/HTTPS/AJP protocols) can be configured directly on the corresponding connectors, using the max-connections attribute, or via a thread pool configuration, as shown below.

<subsystem xmlns="urn:jboss:domain:web:2.2" ... >
    ...
    <connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http" max-connections="200"/>
    <connector name="ajp" protocol="AJP/1.3" scheme="http" socket-binding="ajp" max-connections="200"/>
    <connector name="https" protocol="HTTP/1.1" scheme="https" socket-binding="https" enable-lookups="false" secure="true" max-connections="200">
        ...
    </connector>
    ...
</subsystem>

Thread Pool Configuration

A thread pool must be configured in the "threads" subsystem, as described here:

WildFly Threads Subsystem Configuration

Once the thread pool has been configured, it can be plugged into the HTTP connector as follows:

...
<connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http" executor="http-thread-pool"/>
...

Red Hat Recommendations on the Number of AJP/HTTP Threads

How large should our JBoss AJP or HTTP thread pool be? https://access.redhat.com/solutions/452023

Adding a JBossWeb Global Valve with CLI

Adding a JBossWeb Global Valve with CLI