jGroups bind_addr options in tomcat.javaoptions always bind to 127.0.0.1

[Former Member]

Is anybody else experiencing problems with Hybris 6.5 and jGroups bind address configuration, specifically using the tomcat.javaoptions parameters in local.properties to define the binding to eth0?

We're using the following option in local.properties:

tomcat.javaoptions=-Djgroups.bind_addr=match-interface:eth0 -Djava.net.preferIPv4Stack=true -Djava.net.preferIPv6Addresses=false

which should bind to eth0 and pick up its IP address. This has worked for us with Hybris 5.7. But since using Hybris 6 with Debian 9, the above option binds the IP to localhost (127.0.0.1) and regardless of whatever other options we've applied to bind_addr, including explicitly declaring the IP address (which is something we don't want to do, since we're auto-scaling our Hybris instances), the result is always the same: it is bound to 127.0.0.1. Needless to say, this breaks clustering!

Within the jGroups configuration file (/opt/hybris/bin/platform/ext/core/resources/jgroups-tcp.xml) we can override the variable bind_addr="${hybris.jgroups.bind_addr}" with the IP, and this works - the IP is then properly bound to the right interface and IP. But obviously, with auto-scaling in place, this is not ideal.

My question is - is anybody else experiencing similar issues? Is this likely a bug? Has anything changed in how Hybris deals with wrapper.conf (which is generated from the local.properties file) since version 5.7?

Any assistance greatly appreciated.

Regards,

Martyn

[Former Member · Accepted solution]

The answer to this issue was to add:

cluster.broadcast.method.jgroups.tcp.bind_addr=match-interface:eth0

within local.properties.