These parameters apply in both standalone or managed domain mode:
Name Function
-b=<value> Sets system property jboss.bind.address to <value>. See Controlling the Bind for further details.
Address with -b
-b<name>=<value> Sets system property jboss.bind.address.<name> to <value> where name
can vary. See Controlling the Bind Address with -b for further details.
-u=<value> Sets system property jboss.default.multicast.address to <value>. See for further details.
Controlling the Default Multicast Address with -u --version
-v -V
Prints the version of JBoss AS to standard output and exits the JVM.
--help -h
Prints a help message explaining the options and exits the JVM.
4.8.3 Controlling the Bind Address with -b
JBoss AS binds sockets to the IP addresses and interfaces contained in the <interfaces> elements in
, and . (See and for further
standalone.xml domain.xml host.xml Interfaces Socket Bindings
information on these elements.) The standard configurations that ship with JBoss AS includes two interface configurations: <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> </interfaces>
Those configurations use the values of system properties jboss.bind.address.management and if they are set. If they are not set, 127.0.0.1 is used for each value.
jboss.bind.address
As noted in Common Parameters, the AS supports the -b and -b<name> command line switches. The only function of these switches is to set system properties jboss.bind.address and
respectively. However, because of the way the standard AS configuration jboss.bind.address.<name>
, using this as your launch command causes all
If your interface configurations match those shown above
sockets associated with interface named "public" to be bound to 192.168.100.10.
$JBOSS_HOME/bin/standalone.sh -b=192.168.100.10
In the standard config files, public interfaces are those not associated with server management. Public interfaces handle normal end-user requests.
Interface names
The interface named "public" is not inherently special. It is provided as a convenience. You can name your interfaces to suit your environment.
To bind the public interfaces to all IPv4 addresses (the IPv4 wildcard address), use the following syntax:
$JBOSS_HOME/bin/standalone.sh -b=0.0.0.0
You can also bind the management interfaces, as follows:
$JBOSS_HOME/bin/standalone.sh -bmanagement=192.168.100.10
In the standard config files, management interfaces are those sockets associated with server management, such as the socket used by the CLI, the HTTP socket used by the admin console, and the JMX connector socket.
JBoss Community Documentation Page 99 of 660
Be Careful
The -b switch only controls the interface bindings because the standard config files that ship with JBoss AS sets things up that way. If you change the <interfaces> section in your configuration to ignore the system properties controlled by -b, then setting -b in your launch command will have no effect.
For example, this perfectly valid setting for the "public" interface causes -b to have no effect on the "public" interface:
<interface name="public"> <nic name="eth0"/> </interface>
The key point is the contents of the configuration files determine the configuration. Settings They only provide a shorter syntax for
like-bare not overrides of the configuration files.
setting a system properties that may or may not be referenced in the configuration files. They are provided as a convenience, and you can choose to modify your configuration to ignore them.
4.8.4 Controlling the Default Multicast Address with -u
JBoss AS may use multicast communication for some services, particularly those involving high availability clustering. The multicast addresses and ports used are configured using the socket-binding elements in
and . (See for further information on these elements.) The standalone.xml domain.xml Socket Bindings
standard HA configurations that ship with JBoss AS include two socket binding configurations that use a default multicast address:
<socket-binding name="jgroups-mping" port="0"
multicast-address="${jboss.default.multicast.address:230.0.0.4}" multicast-port="45700"/> <socket-binding name="jgroups-udp" port="55200"
multicast-address="${jboss.default.multicast.address:230.0.0.4}" multicast-port="45688"/>
Those configurations use the values of system property jboss.default.multicast.address if it is set. If it is not set, 230.0.0.4 is used for each value. (The configuration may include other socket bindings for multicast-based services that are not meant to use the default multicast address; e.g. a binding the mod-cluster services use to communicate on a separate address/port with Apache httpd servers.) As noted in Common Parameters, the AS supports the -u command line switch. The only function of this switch is to set system property jboss.default.multicast.address. However, because of the way the standard AS configuration files are set up, using the -u switches can indirectly control how the AS uses multicast.
, using this as your launch command causes
If your socket binding configurations match those shown above
the service using those sockets configurations to be communicate over multicast address 230.0.1.2.
$JBOSS_HOME/bin/standalone.sh -u=230.0.1.2
Be Careful
As with the -b switch, the -u switch only controls the multicast address used because the standard config files that ship with JBoss AS sets things up that way. If you change the
sections in your configuration to ignore the system properties controlled by <socket-binding>
, then setting in your launch command will have no effect.
-u -u
4.9 Subsystem configuration
The following chapters will focus on the high level management use cases that are available through the CLI and the web interface. For a detailed description of each subsystem configuration property, please consult the respective component reference.
JBoss Community Documentation Page 101 of 660 1. 2. 3. 4. 5. Schema Location
The configuration schema can found in $JBOSS_HOME/docs/schema.
4.9.1 Data sources
Datasources are configured through the datasource subsystem. Declaring a new datasource consists of two separate steps: You would need to provide a JDBC driver and define a datasource that references the driver you installed.