search

senecajs / seneca-amqp-transport

Official AMQP transport plugin for Seneca
MIT License
68 stars 25 forks source link

Does this allow for communication across docker-compose containers? #49

Closed chippawah closed 8 years ago

chippawah commented 8 years ago

I'm trying to set up a few microservices that will sit on different docker containers. My thought is that I can have a rabbitMQ container running and then have each microservice on other containers make actions against and listen (with pins) to the rabbitMQ container. Each container has one seneca instance exported to be used by mircoservices within the container. Each instance is using the same amqp url associated with the rabbitMQ container

I'm able to get a container to make a successful action against itself but all other actions timeout. Each of my containers start their instances of seneca and act with a message to a system container. The system container is able to send and receive its own action but all actions sent to it timeout from other containers timeout.

screen shot 2016-09-07 at 12 53 28 pm screen shot 2016-09-07 at 12 53 49 pm

Has anyone successfully used the amqp transport across docker-containers?

chippawah commented 8 years ago

I found what was missing. A client needs a pin even if its role:*,cmd:*. Closing for now but happy to help anyone stuck with this.