-
-
Notifications
You must be signed in to change notification settings - Fork 140
Description
Hi, I start using this package instead of the official AWS SDK over a week ago, and since then I have been having connection issues, while new sending messages to SQS.
I run a serverless setup: "SQS => Lambda trigger" and execute Symfony Messenger with bref/symfony-messenger
During the handling of the messages, new messages are pushed to SQS.
Very occasionally this fails, but I dont understand why. The only difference I can think of with the AWS SDK is that it implements an retry schema.
Does anyone else experience these occasional failures? Some of the errors messages I extracted:
- fopen(https://52.95.120.176/): failed to open stream: Connection timed out
- fopen(https://52.95.112.152/): failed to open stream: HTTP request failed!
- fopen(): SSL: Handshake timed out
- Server returned nothing (no headers, no data) for "https://sqs.eu-west-1.amazonaws.com/".
So I was considering, would it be possible/wise/useful to create a Retry middleware of some sort, that would handle these failures, and retry if appropriate?
The HttpClient should have some support for middlewares according to symfony/symfony#36779
The retry mechanism could mimimic eg https://github.com/aws/aws-sdk-php/blob/master/src/RetryMiddleware.php