Enterprise Distributed Application Service:Error code: HSF-0038

Error message

Multiple network interface controllers (NICs) are configured for the High-speed Service Framework (HSF) provider, and the HSF provider is bound to an incorrect IP address.

Cause

When an HSF provider starts on a host with multiple NICs, the framework automatically selects an IP address to bind to. If the selected IP is unreachable by HSF consumers -- for example, a loopback address or an address on a different subnet -- the provider registers an incorrect address and consumers fail to connect. HSF reports error HSF-0038.

This typically occurs in the following scenarios:

• The host has both a public and a private NIC, and HSF binds to the wrong one.

• A Docker bridge or virtual network adapter is present, and HSF selects its IP instead of the host network IP.

• The host has multiple physical NICs on different subnets.

Identify the bound IP address

Before you apply a fix, determine which IP address HSF is currently bound to and which address is correct.

1. Check the HSF provider startup logs for the bound IP address.

2. List all IP addresses on the host:

   ip addr show

3. Compare the bound IP against the available addresses. The correct IP is the one reachable by HSF consumers over the network used for service communication.

Solution

Add the -Dhsf.server.ip JVM startup parameter to explicitly bind the HSF provider to the correct IP address, bypassing automatic NIC selection:

-Dhsf.server.ip=<correct-ip-address>

Replace <correct-ip-address> with the IP address you identified in the previous step.

Verify the fix

After restarting the application, confirm that the provider registered the correct IP address:

1. Check the HSF provider startup logs for the newly bound IP.

2. Verify that HSF consumers can successfully connect to the provider at the expected IP address.