Uncaught SQS Exception when symfony/messenger worker stopped #1412
Comments
|
|
|
Same issue here: // The worker will automatically exit once it has processed 9 messages, been running for 15s or received a stop signal
// via the messenger:stop-workers command.
// Quit the worker with CONTROL-C.
// Re-run the command with a -vv option to see logs about consumed messages.
PHP Fatal error: Uncaught LogicException: Instance of "Symfony\Component\HttpClient\Response\CurlResponse" is already consumed and cannot be managed by "Symfony\Component\HttpClient\Response\AsyncResponse". A decorated client should not call any of the response's methods in its "request()" method. in /var/www/html/vendor/symfony/http-client/Response/AsyncResponse.php:284
Stack trace:
#0 /var/www/html/vendor/symfony/http-client/Response/AsyncResponse.php(66): Symfony\Component\HttpClient\Response\AsyncResponse::stream(Array, -0.0)
#1 /var/www/html/vendor/symfony/http-client/Response/CommonResponseTrait.php(142): Symfony\Component\HttpClient\Response\AsyncResponse::Symfony\Component\HttpClient\Response\{closure}(Object(Symfony\Component\HttpClient\Response\AsyncResponse), -0.0)
#2 /var/www/html/vendor/symfony/http-client/Response/AsyncResponse.php(96): Symfony\Component\HttpClient\Response\AsyncResponse::initialize(Object(Symfony\Component\HttpClient\Response\AsyncResponse))
#3 /var/www/html/vendor/async-aws/core/src/Response.php(141): Symfony\Component\HttpClient\Response\AsyncResponse->getStatusCode()
#4 /var/www/html/vendor/async-aws/core/src/Response.php(118): AsyncAws\Core\Response->resolve()
#5 [internal function]: AsyncAws\Core\Response->__destruct()
#6 {main}
thrown in /var/www/html/vendor/symfony/http-client/Response/AsyncResponse.php on line 284
Fatal error: Uncaught LogicException: Instance of "Symfony\Component\HttpClient\Response\CurlResponse" is already consumed and cannot be managed by "Symfony\Component\HttpClient\Response\AsyncResponse". A decorated client should not call any of the response's methods in its "request()" method. in /var/www/html/vendor/symfony/http-client/Response/AsyncResponse.php:284
Stack trace:
#0 /var/www/html/vendor/symfony/http-client/Response/AsyncResponse.php(66): Symfony\Component\HttpClient\Response\AsyncResponse::stream(Array, -0.0)
#1 /var/www/html/vendor/symfony/http-client/Response/CommonResponseTrait.php(142): Symfony\Component\HttpClient\Response\AsyncResponse::Symfony\Component\HttpClient\Response\{closure}(Object(Symfony\Component\HttpClient\Response\AsyncResponse), -0.0)
#2 /var/www/html/vendor/symfony/http-client/Response/AsyncResponse.php(96): Symfony\Component\HttpClient\Response\AsyncResponse::initialize(Object(Symfony\Component\HttpClient\Response\AsyncResponse))
#3 /var/www/html/vendor/async-aws/core/src/Response.php(141): Symfony\Component\HttpClient\Response\AsyncResponse->getStatusCode()
#4 /var/www/html/vendor/async-aws/core/src/Response.php(118): AsyncAws\Core\Response->resolve()
#5 [internal function]: AsyncAws\Core\Response->__destruct()
#6 {main}
thrown in /var/www/html/vendor/symfony/http-client/Response/AsyncResponse.php on line 284Using |
|
I switched from FIFO to Standard SQS Queue. Problem disappeared. |
|
Anything changed at this matter? The issue persists: |
|
Same problem. I have tried to investigate, but the code is super complicated... @stof, maybe you have some ideas of where I could begin or how to fix it? I think the bug is due to the option This error begins after I update dependencies in my project. Among them:
I checked the changes but found nothing related to a bug. |
jetrodn
pushed a commit
to jetrodn/aws
that referenced
this issue
May 5, 2024
- added a validation to check for an empty string response content during long polling in AWS SQS - added corresponding unit tests
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi there.
I'm using
symfony/messengerwith SQS transport configuration;async-aws/sqs1.7.0I have two recurring uncaught exceptions from SQS Connection.
I'm not sure, but I think the problem is coming from
aws/async, notsymfony/messenger.Every ~3600 sec, symfony messenger worker is stopped because of time-limit option and is restarted automatically by supervisord.
When worker is stopping (I guess), SQS throw one of the two following uncaught exceptions.
After reading #1218, I tried to increase polling_timeout from default (0.1) to 0.5. I'll keep you informed.
Here the issue on symfony project
The text was updated successfully, but these errors were encountered: