Io WildFly Subsystem Configuration: Difference between revisions
Jump to navigation
Jump to search
(→name) |
No edit summary |
||
Line 23: | Line 23: | ||
==bufffer-pool== | ==bufffer-pool== | ||
=Declaring Different Workers to be Used by Undertow and Remoting= | |||
<pre> | |||
<subsystem xmlns="urn:jboss:domain:io:1.1"> | |||
<!-- this will be used by Undertow --> | |||
<worker name="WORKER1"/> | |||
<!-- this will be used by Remoting --> | |||
<worker name="WORKER2"/> | |||
<buffer-pool name="default"/> | |||
</subsystem> | |||
</pre> |
Revision as of 03:12, 20 January 2016
Internal
Overview
<subsystem xmlns="urn:jboss:domain:io:1.1"> <worker name="default"/> <buffer-pool name="default"/> </subsystem>
Note that the XNIO Worker declared here is shared by both Undertow and Remoting, so a configuration change - including the name - affects both.
Configuration Elements
worker
name
The name of the XNIO Worker shared by Undertow and Remoting subsystems. If the name changes, Undertow's http-listener and Remoting's endpoint element should be changed accordingly.
bufffer-pool
Declaring Different Workers to be Used by Undertow and Remoting
<subsystem xmlns="urn:jboss:domain:io:1.1"> <!-- this will be used by Undertow --> <worker name="WORKER1"/> <!-- this will be used by Remoting --> <worker name="WORKER2"/> <buffer-pool name="default"/> </subsystem>