Docker Community Forums

Share and learn in the Docker community.

Rabbitmq closing connection on windows

beta

(Mattroid) #1

Expected behavior

rabbitmq messaging works normal

Actual behavior

rabbitmq closes the connection prematurely

Information

  • the output of:
    MassTransit.Exceptions.PublishException: At least one exception occurred publishing ShiftWise.Message.Blueprint.MessageDtos.GpsPublish to rabbitmq://localhost/ShiftWise.Message.Blueprint.MessageDtos:GpsPublish —> MassTransit.Exceptions.SendException: rabbitmq://localhost/ShiftWise.Message.Blueprint.MessageDtos:GpsPublish => An exception was thrown during Send —> MassTransit.Transports.InvalidConnectionException: rabbitmq://localhost/ShiftWise.Message.Blueprint.MessageDtos:GpsPublish => Invalid connection to host —> RabbitMQ.Client.Exceptions.AlreadyClosedException: Already closed: The AMQP operation was interrupted: AMQP close-reason, initiated by Peer, code=501, text=“FRAME_ERROR - type 3, first 16 octets = <<”{\r\n “destinatio”>>: {invalid_frame_end_marker,
    0}", classId=0, methodId=0, cause=

-using the rabbitmq 3-managment tag

  • running on windows 10

This has something to do with the localhost port mapping. If I change my rabbitmq connection string from rabbitmq://localhost/ to rabbitmq://docker/ it works.

Steps to reproduce the behavior

  1. run rabbitmq 3-managment
  2. try to get a masstransit application to run on it

(Michael Friis) #2

Sorry about the slow response - there was a bug in the localhost networking proxy that was the likely cause of this. It’s been fixed: https://docs.docker.com/docker-for-windows/release-notes/#/beta-21-release-2016-07-28-1-12-0-beta21