JBossWeb WildFly Subsystem Concepts: Difference between revisions
Jump to navigation
Jump to search
| (One intermediate revision by the same user not shown) | |||
| Line 26: | Line 26: | ||
==Global Valve== | ==Global Valve== | ||
{{Internal|Custom_WildFly_JBossWeb_Valve#Global_Valve|Custom | {{Internal|Custom_WildFly_JBossWeb_Valve#Global_Valve|Custom Global JBossWeb Valve}} | ||
==Context Valve== | ==Context Valve== | ||
{{Internal|Custom_WildFly_JBossWeb_Valve#Context_Valve|Context JBossWeb 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:
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]