28.6. Other Configuration Issues

In the Transport Protocols section above, we briefly touched on how the interface to which JGroups will bind sockets is configured. Let us get into this topic in more depth:

First, it is important to understand that the value set in any bind_addr element in an XML configuration file will be ignored by JGroups if it finds that the system property jgroups.bind_addr (or a deprecated earlier name for the same thing, bind.address) has been set. The system property has a higher priority level than the XML property. If JBoss Enterprise Application Platform is started with the -b (or --host) switch, the application server will set jgroups.bind_addr to the specified value. If -b is not set, the application server will bind most services to localhost by default.

So, what are best practices for managing how JGroups binds to interfaces?

This setting tells JGroups to ignore the jgroups.bind_addr system property, and instead use whatever is specified in XML. You would need to edit the various XML configuration files to set the various bind_addr attributes to the desired interfaces.