Replies: 2 comments 1 reply
-
RabbitMQ logs all connection lifecycle events (for TCP connections that are established and send at least one byte of data). See what it observes happening. Default seeded user can only connection from localhost, by design. Depending on the network setup this may or may not be relevant here. Either way, guessing is a very time consuming way of troubleshooting. I'd take a look at logs instead. |
Beta Was this translation helpful? Give feedback.
-
Thank you for your help, Michael! The problem was my containers was using the old version of the image with obsolet dll's, so it was trying to connect to localhost, even I changing the code. I deleted my image, it builded a new one with the correct configurations and it worked! |
Beta Was this translation helpful? Give feedback.
-
So, this is my docker-compose yml file:
this is my config file which I connect to RabbitMq:
but when I run docker-compose up I still got the error
And the product service can register inside the Service Discovery without a problem, and I followed almost the same steps. And I know that the problem isn't the rabbitmq container taking time to be ready, because I can connect on my machine. And everytime the product service failed to launch, it restarts, but no matter how much time it takes, I still got this error. And the log of the messageBroker container shows it's healthy (and if wasn't, I would not be able to access through my machine ). I don't have any other ideas. Also, to test the port connection, I created a container with ubuntu image, and did telnet host-ip port and it was successfull in connect with the container.
Beta Was this translation helpful? Give feedback.
All reactions