Host.xml

migrating from https://home.feodorov.com:9443/wiki/Wiki.jsp?page=Host.xml

Internal

• WildFly Configuration
• WildFly Domain Mode Configuration

Overview

This file contains configuration details for a specific physical host in a managed domain: the name of the host, network interfaces, socket bindings. This file is not present on standalone servers. The file's location is $JBOSS_HOME/domain/configuration/host.xml.

Schema

The domain.xml configuration syntax is described in $JBOSS_HOME/docs/schema/jboss-as-config_*.xsd

Host Name

The host name specified as <host name="..."> is relevant if when a subordinate host controller connects to a remote domain controller. The host controller will use the host name specified here as "user name" while authenticating against the Management Realm of the domain controller.

The host name can be overridden without modifying the configuration file. The server uses the following precedence in determining the host name:

1. If set, the name <host> element attribute in the host.xml configuration file.

2. The value of the jboss.host.name system property.

3. The value that follows the final period (".") character in the jboss.qualified.host.name system property, or the entire value if there is no final period (".") character.

4. The value that follows the period (".") character in the HOSTNAME environment variable for POSIX-based operating systems, the COMPUTERNAME environment variable for Microsoft Windows, or the entire value if there is no final period (".") character.

TODO, more research needed:

The following mechanism (would be preferred if it worked) does not work:

<host name="${host.id:master}" xmlns="urn:jboss:domain:1.6">
    ...
</host>

where "host.id" is defined in the startup script.

Sections

<interfaces>

<host>
   ...
   <interfaces>
       <interface name="management">
           <inet-address value="${jboss.bind.address.management:127.0.0.1}"/>
       </interface>
       <interface name="public">
          <inet-address value="${jboss.bind.address:127.0.0.1}"/>
       </interface>
       <interface name="unsecure">
           <!-- Used for IIOP sockets in the standard configuration.
                To secure JacORB you need to setup SSL -->
           <inet-address value="${jboss.bind.address.unsecure:127.0.0.1}"/>
       </interface>
    </interfaces>
    ...
</host>

<jvms>

Example:

<host>
    ...
    <jvms>
        <jvm name="default">
            <heap size="64m" max-size="256m"/>
            <permgen size="256m" max-size="256m"/>
            <jvm-options>
                <option value="-server"/>
            </jvm-options>
        </jvm>
    </jvms>
   ...
</host>

<jvm>

<jvm-options>

Example of how to configure GC logging: Enabling GC Logging in Domain Mode - Server Node.

<servers>

Example:

<servers>
    <server name="server-one" group="main-server-group">
        <socket-bindings port-offset="0"/>
        <jvm name="default">
              <jvm-options>
                  <option value="-agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n"/>
              </jvm-options>
        </jvm>
    </server>
    <server name="server-two" group="main-server-group" auto-start="true">
        <socket-bindings port-offset="150"/>
    </server>
    <server name="server-three" group="other-server-group" auto-start="false">
        <socket-bindings port-offset="250"/>
    </server>
</servers>