JBossWeb WildFly Subsystem Concepts: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
 
(12 intermediate revisions by the same user not shown)
Line 5: Line 5:
=Threading Model=
=Threading Model=


JBoss Web connectors use thread pools defined by the [[WildFly_Threads_Subsystem_Concepts#Executor_Model|WildFly Threads Subsystem]].
By default, the JBoss Web connectors use <font color=red>a built-in thread pool. More details required.</font>.


Also see:
The JBoss Web connectors can be configured to use thread pools defined by the [[WildFly_Threads_Subsystem_Concepts#Executor_Model|WildFly Threads Subsystem]]. For an example on how to configure an executor and its associated thread factory for use with a JBossWeb connector in WildFly see:


<blockquote style="background-color: #f9f9f9; border: solid thin lightgrey;">
<blockquote style="background-color: #f9f9f9; border: solid thin lightgrey;">
:[[JBossWeb Concepts#Threading_Model|JBossWeb Threading Model]]
:[[WildFly Threads Subsystem Configuration]]
:[[WildFly_Threads_Subsystem_Concepts#How_Does_it_Relate_to_JBossWeb.3F|WildFly Threads Subsystem Concepts]]
</blockquote>
</blockquote>


External: 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
Aside from the threads that handle requests, JBossWeb uses two more:
 
<pre>
"http-bluehost/1.2.3.4:8080-Acceptor-0" daemon prio=10 tid=0x00002aed88141800 nid=0x7022 runnable [0x00002aed8c402000]
"http-bluehost/1.2.3.4:8080-Poller" daemon prio=10 tid=0x00002aed88140800 nid=0x7020 in Object.wait() [0x00002aed8c301000]
</pre>
 
=Valve=
 
{{Internal|Tomcat_Concepts#Valve|Tomcat Concepts - Valve}}
 
==Global Valve==
 
{{Internal|Custom_WildFly_JBossWeb_Valve#Global_Valve|Custom Global JBossWeb Valve}}
 
==Context Valve==
 
{{Internal|Custom_WildFly_JBossWeb_Valve#Context_Valve|Custom Context JBossWeb Valve}}

Latest revision as of 20:48, 8 March 2017

Internal

Threading Model

By default, the JBoss Web connectors use a built-in thread pool. More details required..

The JBoss Web connectors can be configured to use thread pools defined by the WildFly Threads Subsystem. For an example on how to configure an executor and its associated thread factory for use with a JBossWeb connector in WildFly see:

WildFly Threads Subsystem Configuration

Aside from the threads that handle requests, JBossWeb uses two more:

"http-bluehost/1.2.3.4:8080-Acceptor-0" daemon prio=10 tid=0x00002aed88141800 nid=0x7022 runnable [0x00002aed8c402000]
"http-bluehost/1.2.3.4:8080-Poller" daemon prio=10 tid=0x00002aed88140800 nid=0x7020 in Object.wait() [0x00002aed8c301000]

Valve

Tomcat Concepts - Valve

Global Valve

Custom Global JBossWeb Valve

Context Valve

Custom Context JBossWeb Valve