Unable to create producer when connected to localhost and rabbit uses a hostname

[Zerpet]

Describe the bug

From this conversation: spring-projects/spring-amqp#2522

When RabbitMQ is running in a environment where rabbit node name is not resolvable by the clients, and the client connects locally via the loopback, the client library fails to create a producer and retries infinitely.

This kind of setups are common for local development environments, where rabbit may resolve its node name as foobar, and the client connects via localhost. One example is running rabbit locally, and another, running rabbit in a container.

Reproduction steps

1. Start RabbitMQ in a container, with a specific hostname

   docker run --hostname foobar --rm --name bunny -p 5672:5672 -p 15672:15672 -p 5552:5552 rabbitmq:3-management
   docker exec bunny rabbitmq-plugins enable rabbitmq_stream_management
   

2. Create a StreamSystem that connects to localhost and default port 5552
3. Create a stream
4. Create a producer using Producer.Create()

Observe that the client does not create the producer connection, and it retries infinitely.

Expected behavior

The client library connects via localhost, or gives up connecting.

Additional context

Related rabbitmq/rabbitmq-server#9424

The issue can be workarounded using an address resolver, or changing the advertised host/port to always be localhost and the default stream port. However, there's a fair point made in the Spring Boot discussion: spring-projects/spring-amqp#2522 (comment). In summary, if there's no load balancer involved (address resolved was created for LB setups), and there's no rabbit cluster, then the localhost and default loopback user configuration should work.

This may arguably be an improvement, rather than a bug.

[aeb-dev]

I am not sure whether this is the same issue here is my environment:

Deployed to windows wsl kind.
Accessing through nodeport.
Rabbitmq version RabbitMQ 3.13.0-beta.6

AddressResolver = new AddressResolver(new DnsEndPoint("localhost", 30552)),
Endpoints = new List<EndPoint> { new DnsEndPoint("localhost", 30552) },

If I don't provide AddressResolver creating consumer and producer fails
if I don't provide Endpoints creating streams fails

[MikhailTushev]

you need add advertised_host localhost for rmq
example of docker compose without enabled plugin :

rabbitmq:
    container_name: rabbitmq
    image: rabbitmq:3.11-management
    ports:
      - 5552:5552
      - 5672:5672
      - 15672:15672
    volumes:
      - ~/.docker-conf/rabbitmq/data/:/var/lib/rabbitmq/
      - ~/.docker-conf/rabbitmq/log/:/var/log/rabbitmq
    environment:
      - RABBITMQ_SERVER_ADDITIONAL_ERL_ARGS=-rabbitmq_stream advertised_host localhost

[Zerpet]

I am not sure whether this is the same issue here is my environment:

Deployed to windows wsl kind. Accessing through nodeport. Rabbitmq version RabbitMQ 3.13.0-beta.6

AddressResolver = new AddressResolver(new DnsEndPoint("localhost", 30552)),
Endpoints = new List<EndPoint> { new DnsEndPoint("localhost", 30552) },

If I don't provide AddressResolver creating consumer and producer fails if I don't provide Endpoints creating streams fails

This is related in a slightly different setup. The Endpoints must be provided always in your case, because you are using a non-standard port (since you are exposing via NodePort). After resolving this issue, you will not need to provide the AddressResolver.

[Zerpet]

you need add advertised_host localhost for rmq

After resolving this issue, you won't even need to advertise the host/port 🙂