SQS responds with an error, but no catch is executed #4092
adrian-goe
started this conversation in
General
Replies: 1 comment
-
Hi @adrian-goe, thank you for reaching out. In order to attempt to reproduce the reported issue, could you please provide the following:
const sqsClient = new SQSClient({region: 'REGION'});
// Set the parameters
const params = {
DelaySeconds: 10,
MessageAttributes: {
Title: {
DataType: "String",
StringValue: "Testing Message",
},
Author: {
DataType: "String",
StringValue: "Yenfry Herrera",
},
WeeksOn: {
DataType: "Number",
StringValue: "6",
},
},
MessageBody: "A TEXT OVER THE LIMIT(2KB)",
QueueUrl: "https://sqs.{REGION}.amazonaws.com/{ACCOUNT_ID}/{QUEUE-NAME}"
};
await sqsClient.send(new SendMessageCommand(params))
.then((value)=>{console.log('Value: ', value);})
.catch((reason)=>{console.log('Error: ', reason)}); I will be also moving this issue to the right repo! Thank you! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Confirm by changing [ ] to [x] below:
Describe the question
Hi, wie tried to send messages to SQS. In our setup, the max_message_size was limited to 2kb, without someone remembering it. Removing the limit fixed our bug. But finding this, was a struggle with some the following question.
So we tried to send messages SQS:
We were wondering, why it says, that messages were send, but dosn't apper in sqs.
After some unsuccessful debugging, we change the
then()
this:The results are a bit surprising.
The httpCode is 200 but it's a failing request. My expectation would be, that this failed request would result in an error, that goes to the catch blog.
Is there a reason for this behavior? It feels wrong.
We use
"@aws-sdk/client-sqs": "3.72.0"
Beta Was this translation helpful? Give feedback.
All reactions