Closed kcjl519 closed 6 years ago
@kcjl519 Did you ever resolve this issue? I am experiencing the same error using 2 rails apps and propono.
@A-Scott-Rowe, no, I was stuck actually. It was working a year ago and now it doesn't. I can't see why.
Could you give more details, please? Do you use the same docker-compose configuration?
@s12v I think my situation was actually a little different. I was using this in a docker container and also a fake sqs in another docker container. The two services worked great independently but when sns tried to connect to sqs to push the message it received a similar(but not the same) error as above.
I was using the same config as in your example but could not resolve it. I ended up finding an all-in-one docker image that works very well. https://github.com/p4tin/GoAws
@s12v is this project abandoned? I'm having the problem above and I don't know how to debug this. I have verified that my ElasticMQ container is accessible from my s12v/sns container on the correct port, but I'm still getting the "Connection refused" error message above.
Any hints on how to debug would be greatly appreciated.
@scott-r-lindsey, it's not abandoned, but I couldn't find the root cause of this problem and didn't have time to look into this again.
@s12v I can reproduce this issue using the example docker-compose file that is include in your project. The problem appears to be that when the camel component that is used to send the message to sqs starts up it lists the queues to get their urls. If elasticmq has not been configured with a host name that matches the docker link then it will try to send the message to the wrong url.
I have submitted a pull request that shows the fix.
this should be solved now, thanks @sam-io
I have a very basic docker-compose configuration, with 2 nodes. nodejs docker is linked via docker link as well as dependency
The following are the api calls I'm using to test.
Create new topic
Export ARN into env
Subscribe nodejs to topic
Post new message
And I get the following errors in Akka (with debug turned on)
I have manually subscribed the nodejs's IP, and it published message fine, I have also subscribed google.com to it, and it published fine. It seems Akka is unable to resolve the DNS of the docker link for nodejs.