-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not being able to Publish to SQS/SNS with v1 #140
Comments
Merged
hi @maganuk I've pushed a fix that should address the incorrect policy. I haven't been able to reproduce the "one in 5" issue you mention, could you provide a bit more info about your setup or possibly a code sample so I can get the same bug? |
@adenhertog I dont know what went wrong, but I just changed the queue name and it started working with the new policy. Thanks. Closing this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I just upgraded the packages to v1. The queues, topics and subscriptions are being created correctly and debugger is showing that its publishing a message to sqs with the correct queue and topic name / arns, however no message is getting published to the actual queue. Polling on both the sending and receiving end is showing 0 messages. Any suggestions?
UPDATE: Further investigations reveal, that this is working very, very intermittently. It definitely is not working with the default queue policy, works once every 5 times that too if I specify the queue policy (strange since I'm using the default policy from the GeneratePolicy method). I think there might be an Async issue somewhere. This is working fine with the in-memory transport
Thanks
Vishal
The text was updated successfully, but these errors were encountered: