The expected behavior is that for each TCP or UDP service, the service can be configured
to listen on either 0.0.0.0 (the default), or a specific IP address/hostname, where the
address may be localhost (127.0.0.1). A "TCP or UDP service" include all listeners,
anything that listens on a port, etc.
Exceptions to the 0.0.0.0 default are:
the OSGi console that listens on port 6666 - default 127.0.0.1
admin-listener - possibly default to 127.0.0.1 (See issue 11626)
Whenever the DAS, an instance, or asadmin is a client of a service, it determines the
address of the service by consulting the appropriate configuration information. If that
address is 0.0.0.0, then the hostname for the service is determined by looking at the
<node> entry for the server that hosts the service.
The configuration of an address for a specific service is provided by using the "address"
attribute of the element that defines the listener for the service. For example:
<network-listener address="somehost" port="8080" protocol="http-listener-1"
transport="tcp" name="http-listener-1" thread-pool="http-thread-pool" />
This proposal does not yet address the request in issue 4362, which is to ease deployment
on a multi-homed system. Also need to confirm that every service uses the "address"
attribute to specify an address.