JBoss.orgCommunity Documentation

Chapter 9. Server-side Configuration Properties

9.1. Proxy Discovery Configuration
9.2. Proxy Configuration
9.3. SSL Configuration
9.4. HA Configuration
9.5. Load Configuration for JBoss Web and Tomcat

The tables below enumerate the configuration properties available to an application server node. The location for these properties depends on how mod_cluster is configured.

The list of proxies from which an application expects to receive AJP connections is either defined statically, via the addresses defined in the proxyList configuration property; or discovered dynamically via the advertise mechanism. Using a special mod_advertise module, proxies can advertise their existence by periodically broadcasting a multicast message containing its address/port. This functionality is enabled via the advertise configuration property. If configured to listen, a server can learn of the proxy's existence, then notify that proxy of its own existence, and update its configuration accordingly. This frees both the proxy and the server from having to define static, environment-specific configuration values.


Defines a comma delimited list of httpd proxies with which this node will initially communicate. Value should be of the form:


Using the default configuration, this property can by manipulated via the jboss.mod_cluster.proxyList system property.

excludedContextsROOT, admin-console, invoker, bossws, jmx-console, juddi, web-consoleConfiguration

List of contexts to exclude from httpd registration, of the form:


If no host is indicated, it is assumed to be the default host of the server (e.g. localhost). "ROOT" indicates the root context. Using the default configuration, this property can by manipulated via the jboss.mod_cluster.excludedContexts system property.


If false the contexts are registered disabled in httpd, they need to be enabled via the enable() mbean method or via mod_cluster_manager.


The amount of time, measure in units specified by stopContextTimeoutUnit, for which to wait for clean shutdown of a context (completion of pending requests for a distributable context; or destruction/expiration of active sessions for a non-distributable context).


The unit of time for use with stopContextTimeout


Indicates the session draining strategy used during undeployment of a web application. There are three possible values:


Drain sessions before web application undeploy only if the web application is non-disributable.


Always drain sessions before web application undeploy, even for distributable web applications.


Do not drain sessions before web application undeploy, even for non-distributable web application.

proxyURLNoneApache HTTPD

If defined, this value will be prepended to the URL of MCMP commands.


Number of milliseconds to wait for a response from an httpd proxy to MCMP commands before timing out, and flagging the proxy as in error.

true, if proxyList is undefined, false otherwiseConfiguration

If enabled, httpd proxies will be auto-discovered via multicast announcements. This can be used either in concert or in place of a static proxyList.

advertiseGroupAddress224.0.1.105Apache HTTPD

UDP address on which to listen for httpd proxy multicast advertisements

advertisePort23364Apache HTTPD

UDP port on which to listen for httpd proxy multicast advertisements

advertiseSecurityKeyNoneApache HTTPD

If specified, httpd proxy advertisements checksums will be verified using this value as a salt


The thread factory used to create the background advertisement listener.

jvmRouteFactorynew SystemPropertyJvmRouteFactory(new UUIDJvmRouteFactory(), "jboss.mod_cluster.jvmRoute")Configuration Defines the strategy for determing the jvm route of a node, if none was specified in server.xml. The default factory first consults the jboss.mod_cluster.jvmRoute system property. If this system property is undefined, the jvm route is assiged a UUID.

The following configuration values are sent to proxies during server startup, when a proxy is detected via the advertise mechanism, or during the resetting of a proxy's configuration during error recovery.


Indicates whether subsequent requests for a given session should be routed to the same node, if possible.


Indicates whether the httpd proxy should remove session stickiness in the event that the balancer is unable to route a request to the node to which it is stuck. This property is ignored if stickySession is false.


Indicates whether the httpd proxy should return an error in the event that the balancer is unable to route a request to the node to which it is stuck. This property is ignored if stickySession is false.


Number of seconds to wait for a worker to become available to handle a request. When all the workers of a balancer are usable, mod_cluster will retry after a while (workerTimeout/100) to find an usable worker. That is timeout in the balancer mod_proxy documentation. A value of -1 indicates that the httpd will not wait for a worker to be available and will return an error if none is available.


Number of times an httpd proxy will attempt to send a given request to a worker before giving up. The minimum value is 1, meaning try only once. (Note that mod_proxy default is also 1: no retry).


Enables/disables packet flushing


Time to wait before flushing packets. A value of -1 means wait forever.


Time (in seconds) in which to wait for a pong answer to a ping

smaxDetermined by httpd configurationNode

Soft maximum idle connection count (that is the smax in worker mod_proxy documentation). The maximum value depends on the httpd thread configuration (ThreadsPerChild or 1).


Time to live (in seconds) for idle connections above smax


Timeout (in seconds) for proxy connections to a node. That is the time mod_cluster will wait for the back-end response before returning error. That corresponds to timeout in the worker mod_proxy documentation. A value of -1 indicates no timeout. Note that mod_cluster always uses a cping/cpong before forwarding a request and the connectiontimeout value used by mod_cluster is the ping value.


The balancer name


If specified, load will be balanced among jvmRoutes withing the same load balancing group. A loadBalancingGroup is conceptually equivalent to a mod_jk domain directive. This is primarily used in conjunction with partitioned session replication (e.g. buddy replication).

The communication channel between application servers and httpd proxies uses HTTP by default. This channel can be secured using HTTPS by setting the ssl property to true.


This HTTP/HTTPS channel should not be confused with the processing of HTTP/HTTPS client requests.


Should connection to proxy use a secure socket layer

sslCiphersThe default JSSE cipher suites

Overrides the cipher suites used to init an SSL socket ignoring any unsupported ciphers


Overrides the default SSL socket protocol.

sslCertificateEncodingAlgorithmThe default JSSE key manager algorithm

The algorithm of the key manager factory

sslKeyStoreSystem.getProperty("user.home") + "/.keystore"

The location of the key store containing client certificates


The password granting access to the key store


The type of key store

sslKeyStoreProviderThe default JSSE security provider

The key store provider

sslTrustAlgorithmThe default JSSE trust manager algorithm

The algorithm of the trust manager factory


The alias of the key holding the client certificates in the key store


Certificate revocation list


The maximum length of a certificate held in the trust store


The location of the file containing the trust store


The password granting access to the trust store.


The trust store type


The trust store provider

Additional configuration properties when mod_cluster is configured in clustered mode.


If the loadBalancingGroup directive is used, should HA partition use a singleton master per loadBalancingGroup.

Additional configuration properties used when mod_cluster is configured in JBoss Web standalone or Tomcat.


Class name of an object implementing org.jboss.load.metric.LoadMetric


The capacity of the load metric defined via the loadMetricClass property


The number of historic load values to consider in the load balance factor computation.


The factor by which a historic load values should degrade in significance.