JBossWeb WildFly Subsystem Concepts: Difference between revisions
Jump to navigation
Jump to search
| Line 16: | Line 16: | ||
<blockquote style="background-color: #f9f9f9; border: solid thin lightgrey;"> | <blockquote style="background-color: #f9f9f9; border: solid thin lightgrey;"> | ||
:[[JBossWeb | :[[JBossWeb Concepts#Threading_Model|JBossWeb Threading Model]] | ||
</blockquote> | </blockquote> | ||
Revision as of 19:55, 21 February 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:
For more details on the JBossWeb threading model, 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]