INFO message "No host/bind address specified: Using localhost xxxxxxxxx.xxxx" observed in Tanzu GemFire server logs

Products

• VMware Tanzu Data Suite
• VMware Tanzu Gemfire

Issue/Introduction

During Tanzu GemFire member startup or function execution, the following informational message is continuously or repeatedly observed in the cache server log files:

[info 2026/05/16 09:47:24.302 IST nodename <Function Execution Processor39> tid=0x5a26] No host/bind address specified: Using localhost xxxxxx.xxxx 

• Note: This message may appear even if the primary bind-address parameter has already been explicitly configured in the gemfire.properties file.

Cause

In the GemFire source code architecture, the parameter controlling this channel is initialized with a blank default configuration:

If http-service-bind-address is omitted or left blank, GemFire then systematically falls back to resolving the host machine's primary OS-level Fully Qualified Domain Name (FQDN) or IP, generating the [info] log entry.

Resolution

While this message is informational and indicates a safe fallback mechanism, it is best practice to explicitly declare

If http-service-bind-address is set, then the Tanzu GemFire member binds the embedded HTTP service to the specified address. If this property is not set but the HTTP service is enabled using http-service-port, then Tanzu GemFire binds the HTTP service to the member’s local address. Used by the Tanzu GemFire Pulse Web application and the developer REST API service.

To resolve the symptom and explicitly bind the HTTP engine, apply the following resolution:

Step 1: Update Configuration
Add the http-service-bind-address property to your gemfire.properties file:
Eg:
http-service-bind-address=10.x.x.x

Step 2: Alternatively can add in server start up command:
Eg:
start server --name=<servername> --http-service-bind-address=10.x.x.x 

Additional Information

https://techdocs.broadcom.com/us/en/vmware-tanzu/data-solutions/tanzu-gemfire/10-1/gf/reference-topics-gemfire_properties.html