JBossWeb WildFly Subsystem Concepts: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 18: | Line 18: | ||
:[[JBossWeb Concepts#Threading_Model|JBossWeb Threading Model]] | :[[JBossWeb Concepts#Threading_Model|JBossWeb Threading Model]] | ||
</blockquote> | </blockquote> | ||
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> | |||
Revision as of 22:23, 8 June 2016
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]