JBossWeb WildFly Subsystem Concepts: Difference between revisions
Jump to navigation
Jump to search
| 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]]. For an example on how to configure an executor and its associated thread factory for use with a JBossWeb connector in WildFly see: | By default, the JBoss Web connectors use <font color=red>a built-in thread pool. More details required.</font>. | ||
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;"> | ||
Revision as of 21:50, 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: