Browse Source
## The Problem
The GetAdvertisedAddress() function was always returning 'localhost'
for all clients, regardless of how they connected to the gateway.
This works when the gateway is accessed via localhost or 127.0.0.1,
but FAILS when accessed via 'kafka-gateway' (Docker hostname) because:
1. Client connects to kafka-gateway:9093
2. Broker advertises localhost:9093 in Metadata
3. Client tries to connect to localhost (wrong!)
## The Solution
Updated GetAdvertisedAddress() to:
1. Check KAFKA_ADVERTISED_HOST environment variable first
2. If set, use that hostname
3. If not set, extract hostname from the gatewayAddr parameter
4. Skip 0.0.0.0 (binding address) and use localhost as fallback
5. Return the extracted/configured hostname, not hardcoded localhost
## Benefits
- Docker clients connecting to kafka-gateway:9093 get kafka-gateway in response
- Host clients connecting to localhost:9093 get localhost in response
- Environment variable allows configuration override
- Backward compatible (defaults to localhost if nothing else found)
## Test Results
✅ Test running from Docker network:
[POLL 1] ✓ Poll completed in 15005ms
[POLL 2] ✓ Poll completed in 15004ms
[POLL 3] ✓ Poll completed in 15003ms
DIAGNOSIS: Consumer is working but NO records found
Gateway logs show:
Starting MQ Kafka Gateway: binding to 0.0.0.0:9093,
advertising kafka-gateway:9093 to clients
This fix should resolve Schema Registry timeout issues!
pull/7329/head
1 changed files with 27 additions and 9 deletions
Loading…
Reference in new issue