Skip to content
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

Consumer is not working on AWS - NestJS #44

Open
eliasjtg opened this issue Jan 27, 2023 · 2 comments
Open

Consumer is not working on AWS - NestJS #44

eliasjtg opened this issue Jan 27, 2023 · 2 comments

Comments

@eliasjtg
Copy link

Hi. I just implemented the SQS queries. It calls the nestjs server, but this is not calling the handler correctly. It isn't logging any error messages or even entering in the handler. I verified that the handler is being called correctly, but still it doesn't do anything. This is only happning when using AWS, since, locally it works just fine.

2023-01-27T15:09:14.908Z	d4978ef1-adc9-5f25-91e1-d2bc4683894e	INFO	{
  Records: [
    {
      messageId: '52ef80c0-02e0-40f7-a361-4f1c51bf13bc',
      receiptHandle: 'AQEB4y3zSc9MmN/l5Mdpfas2yPTBbpl1KmfwckkP8enLrbumKnnMeFX4jE2TC6jvW0NGuQPzsfaDELa73UZkqJTPupHDT1vel8ipzYKVhdExXsPgjgG9T/4JGq2bogXxuM5CA2coGCCg0IqBA3y3pYcWbSzQJ9rnQPvcmLTlDVsZbvE96DzGEbnoYFhepiohUCJP/JKVrF+w1L07RZ7eMEn4OCAJtp2su84j0hoq6g9tC1b+I8vyzyXCVx7MfdNaL6qdiAldSkaIs1NYN33U62ZUMNJO9jJurs9XhP43QZ8ZCaKuGhBGbxAJFTCQC8IOQ7paltwHLB+H+ex/t+1Y3ygW6ZkBUcNZ+Etck+HQAmOsnjez65eYpCnnAqYQUFBRdT85U7tgFaX5LzXhLA3/Vsxy/Q==',
      body: '63d3e8d2f8d244ae1a9dec86',
      attributes: [Object],
      messageAttributes: [Object],
      md5OfMessageAttributes: 'a0c076cee46e48e232dc8c31996a2abe',
      md5OfBody: '4c4c406dc49e40e27c5b83ea0ef07fc2',
      eventSource: 'aws:sqs',
      eventSourceARN: 'arn:aws:sqs:us-east-1:???:SearchDriverBooking',
      awsRegion: 'us-east-1'
    }
  ]
}
@LuiFerPereira
Copy link

Hi, any solution? I have the same problem: The consumer don't logging any error but messages aren't consuming

@ssut
Copy link
Owner

ssut commented Jul 12, 2024

Please let me know so I can investigate it: I’m not sure, but do you think the same problem still exists in the latest version or in the pre-release version in PR #85? (You guys may need to build this yourselves in this case but it would be very helpful if you guys could let me know the result.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants