Server-side Configuration Properties - Proxy Discovery
This topic has not yet been written. The content below is from the topic description.
8.1. Proxy Discovery Configuration 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. Attribute Default Description proxyList None Defines a comma delimited list of httpd proxies with which this node will initially communicate. Value should be of the form: address1:port1,address2:port2 Using the default configuration, this property can by manipulated via the jboss.modcluster.proxyList system property. excludedContexts ROOT, admin-console, invoker, bossws, jmx-console, juddi, web-console List of contexts to exclude from httpd registration, of the form: host1:context1,host2:context2,host3:context3 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.modcluster.excludedContexts system property. autoEnableContexts true If false the contexts are registered disabled in httpd, they need to be enabled via the enable() mbean method or via mod_cluster_manager. stopContextTimeout 10 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). stopContextTimeoutUnit TimeUnit.SECONDS The unit of time for use with stopContextTimeout sessionDrainingStrategy org.jboss.modcluster.SessionDrainingStrategyEnum.DEFAULT Indicates the session draining strategy used during undeployment of a web application. There are three possible values: DEFAULT Drain sessions before web application undeploy only if the web application is non-disributable. ALWAYS Always drain sessions before web application undeploy, even for distributable web applications. NEVER Do not drain sessions before web application undeploy, even for non-distributable web application. proxyURL None If defined, this value will be prepended to the URL of MCMP commands. socketTimeout 20000 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 otherwise 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. advertiseGroupAddress 224.0.1.105 UDP address on which to listen for httpd proxy multicast advertisements advertisePort 23364 UDP port on which to listen for httpd proxy multicast advertisements advertiseSecurityKey None If specified, httpd proxy advertisements checksums will be verified using this value as a salt advertiseThreadFactory Executors.defaultThreadFactory() The thread factory used to create the background advertisement listener. jvmRouteFactory new SystemPropertyJvmRouteFactory(new UUIDJvmRouteFactory(), "jboss.mod_cluster.jvmRoute") 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.