executor="HTTPThreadPool" parameter in EAP 6

Solution Unverified - Updated -

Issue

  • The application vendor has suggested to put in executor="HTTPThreadPool" parameter in the web subsystem.we do not have it in the existing config file(attached domain.xml) and everything looks to be working fine.
  • We wanted to understand what the executor="HTTPThreadPool" parameter in the web subsystem does and if it is required or if there is a default that gets picked up.
Thread Subsystem: -
           <subsystem xmlns="urn:jboss:domain:threads:1.1">
                <bounded-queue-thread-pool name="HTTPThreadPool" allow-core-timeout="true">
                    <core-threads count="${http.threadpool.corethreads:100}"/>
                    <queue-length count="${http.threadpool.queuelength:500}"/>
                    <max-threads count="${http.threadpool.maxthreads:100}"/>
                    <keepalive-time time="${http.threadpool.keepalivetime.seconds:60}" unit="seconds"/>
                </bounded-queue-thread-pool>
            </subsystem>

Web subsystem: - 

            <subsystem xmlns="urn:jboss:domain:web:2.1" default-virtual-server="default-host" instance-id="${jboss.node.name}" native="true">
                <connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http"/>
                <connector name="HTTPS" protocol="HTTP/1.1" scheme="https" socket-binding="https" secure="true" max-connections="${http.threadpool.maxthreads:100}">
                </connector>

Environment

  • Red Hat JBoss Enterprise Application Platform
    • 6.3.2

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.