Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>you can tune the HTTP Conector of the AS7 web subsystem. The available attributes you can tune for the HTTP Connector are described here <a href="http://docs.jboss.org/jbossweb/7.0.x/config/http.html" rel="nofollow">The Http Connector</a>. To define the max-connections for this connector you need change it in $JBOSS_HOME/standalone/configuration/standalone.xml or $JBOSS_HOME/domain/configuration/domain.xml</p> <p>See this piece of configuration:</p> <pre><code>&lt;subsystem xmlns="urn:jboss:domain:web:1.1" default-virtual-server="default-host" native="false"&gt; &lt;connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http" max-connections="250"/&gt; ... &lt;/subsystem&gt; </code></pre> <p>To define a thread pool specific for the HTTP Connector you need to use the AS7 threads subsystem like this one:</p> <pre><code>&lt;subsystem xmlns="urn:jboss:domain:threads:1.0"&gt; &lt;bounded-queue-thread-pool name="http-executor" blocking="true"&gt; &lt;core-threads count="10" per-cpu="20" /&gt; &lt;queue-length count="10" per-cpu="20" /&gt; &lt;max-threads count="10" per-cpu="20" /&gt; &lt;keepalive-time time="10" unit="seconds" /&gt; &lt;/bounded-queue-thread-pool&gt; &lt;/subsystem&gt; </code></pre> <p>and then you need to reference it in the executor attribute of the HTTP Connector. See this piece of config:</p> <pre><code>&lt;subsystem xmlns="urn:jboss:domain:web:1.1" default-virtual-server="default-host" native="false"&gt; &lt;connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http" max-connections="250" executor="http-executor"/&gt; ... &lt;/subsystem&gt; </code></pre> <p>For more details about tuning the AS7 see this post <a href="http://www.mastertheboss.com/jboss-performance/jboss-as-7-performance-tuning/page-4" rel="nofollow">JBoss AS 7 Performance tuning - Tuning Web server thread pool</a> on the masterjboss.com.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload