JBossWeb WildFly Subsystem Configuration: Difference between revisions
Jump to navigation
Jump to search
(Created page with "=Internal= * JBossWeb WildFly Subsystem") |
|||
| (13 intermediate revisions by the same user not shown) | |||
| Line 2: | Line 2: | ||
* [[JBossWeb WildFly Subsystem#Subjects|JBossWeb WildFly Subsystem]] | * [[JBossWeb WildFly Subsystem#Subjects|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 <tt>max-connections</tt> attribute, or via a thread pool configuration, as shown [[#Thread_Pool_Configuration|below]]. | |||
<pre> | |||
<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> | |||
</pre> | |||
==Thread Pool Configuration== | |||
A thread pool must be configured in the "threads" subsystem, as described here: | |||
<blockquote style="background-color: #f9f9f9; border: solid thin lightgrey;"> | |||
:[[WildFly Threads Subsystem Configuration]] | |||
</blockquote> | |||
Once the thread pool has been configured, it can be plugged into the HTTP connector as follows: | |||
<pre> | |||
... | |||
<connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http" executor="http-thread-pool"/> | |||
... | |||
</pre> | |||
==Red Hat Recommendations on the Number of AJP/HTTP Threads== | |||
<blockquote style="background-color: AliceBlue; border: solid thin LightSteelBlue;"> | |||
:How large should our JBoss AJP or HTTP thread pool be? https://access.redhat.com/solutions/452023<br> | |||
</blockquote> | |||
==AJP/HTTP JMX Thread Statistics Monitoring== | |||
{{Internal|WildFly JBossWeb Tomcat Connector Internal ThreadPool Statistics|AJP/HTTP JMX Thread Statistics Monitoring}} | |||
=Adding a JBossWeb Global Valve with CLI= | |||
{{Internal|WildFly_CLI_-_Add_a_JBossWeb_Global_Valve|Adding a JBossWeb Global Valve with CLI}} | |||
Latest revision as of 17:47, 10 May 2017
Internal
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:
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