Configuring the Tomcat Connector for a single instance of JBoss AS

Edit the .properties files in the mod_jk/conf directory to define the Tomcat instance (also known as a Tomcat worker) for the JBoss AS instance.
Note: The following are examples of .properties files used to configure a typical single-node JBoss AS deployment. Analyze your configuration and adjust these settings accordingly.

To configure the Tomcat Connector for a single-node JBoss AS deployment:

  1. Edit the uriworkermap.properties file to define the nodes for your deployment.
    For example: 
    /nexj/*=node1
  2. Edit the workers.properties file to configure the nodes and their properties.
    For example, in a typical NexJ deployment, the configuration in the workers.properties file might look like:
    
worker.list=node1

worker.node1.host=localhost
worker.node1.port=8009
worker.node1.type=ajp13 
worker.node1.lbfactor=1

worker.node1.retries=2 
worker.node1.recovery_options=7
worker.node1.connection_pool_size=256
worker.node1.connection_pool_timeout=300
worker.node1.socket_keepalive=true 
worker.node1.socket_timeout=0
worker.node1.socket_connect_timeout=5000
    In the configuration, the following suggested values are used:
    worker.nodename.type
    The value is always ajp13. Other worker types are unsupported.
    worker.nodename.retries
    Suggested value is 2. The maximum number of times that the node will try to establish a connection to the server after a communication error.
    worker.nodename.recovery_options

    Suggested value is 7. This value is a bitmask. It indicates that, when an error occurs that prevents a complete AJP request from being sent, the server will not retry the request and will close the AJP connection. This prevents automatic request and response duplication.

    worker.nodename.connection_pool_size

    Suggested value is 256. The lower of the maximum Tomcat/JBoss AJP listener thread count and the maximum web server thread count.

    To determine the maximum Tomcat/JBoss AJP listener thread count: In the deploy/jbossweb.sar/server.xml file, refer to the maxThreads attribute for the Connector component for AJP.

    To determine the maximum web server thread count: Refer to Apache or IIS configuration to find the maximum number of web requests that the server can process concurrently.

    worker.nodename.connection_pool_timeout
    Suggested value is 300. The number of seconds after which the idle connections in the pool are closed.
    worker.nodename.socket_keepalive
    Suggested value is true. Sends TCP keepalive messages to maintain the connection.
    worker.nodename.socket_timeout
    Suggested value is 0. Indicates that IIS should wait for the server response indefinitely.
    worker.nodename.socket_connect_timeout
    Suggested value is 5000. The number of milliseconds after which the attempted connection establishment times out.

    A single-node configuration file does not include any properties related to load balancing.

    Note: Refer to the Apache Tomcat documentation for the list and description of all configurable worker properties: http://tomcat.apache.org/connectors-doc/reference/workers.html.
  3. If you are configuring an existing web server that is currently running, restart the web server after modifying the configuration files.