-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[Messenger] prevent infinite redelivery loops and blocked queues #34107
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
<?php | ||
|
||
/* | ||
* This file is part of the Symfony package. | ||
* | ||
* (c) Fabien Potencier <fabien@symfony.com> | ||
* | ||
* For the full copyright and license information, please view the LICENSE | ||
* file that was distributed with this source code. | ||
*/ | ||
|
||
namespace Symfony\Component\Messenger\Exception; | ||
|
||
/** | ||
* @author Tobias Schultze <http://tobion.de> | ||
* | ||
* @experimental in 4.3 | ||
*/ | ||
class RejectRedeliveredMessageException extends RuntimeException | ||
{ | ||
} |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,50 @@ | ||
<?php | ||
|
||
/* | ||
* This file is part of the Symfony package. | ||
* | ||
* (c) Fabien Potencier <fabien@symfony.com> | ||
* | ||
* For the full copyright and license information, please view the LICENSE | ||
* file that was distributed with this source code. | ||
*/ | ||
|
||
namespace Symfony\Component\Messenger\Middleware; | ||
|
||
use Symfony\Component\Messenger\Envelope; | ||
use Symfony\Component\Messenger\Exception\RejectRedeliveredMessageException; | ||
use Symfony\Component\Messenger\Stamp\ReceivedStamp; | ||
use Symfony\Component\Messenger\Transport\AmqpExt\AmqpReceivedStamp; | ||
|
||
/** | ||
* Middleware that throws a RejectRedeliveredMessageException when a message is detected that has been redelivered by AMQP. | ||
* | ||
* The middleware runs before the HandleMessageMiddleware and prevents redelivered messages from being handled directly. | ||
* The thrown exception is caught by the worker and will trigger the retry logic according to the retry strategy. | ||
* | ||
* AMQP redelivers messages when they do not get acknowledged or rejected. This can happen when the connection times out | ||
* or an exception is thrown before acknowledging or rejecting. When such errors happen again while handling the | ||
* redelivered message, the message would get redelivered again and again. The purpose of this middleware is to prevent | ||
* infinite redelivery loops and to unblock the queue by republishing the redelivered messages as retries with a retry | ||
* limit and potential delay. | ||
* | ||
* @experimental in 4.3 | ||
* | ||
* @author Tobias Schultze <http://tobion.de> | ||
*/ | ||
class RejectRedeliveredMessageMiddleware implements MiddlewareInterface | ||
{ | ||
public function handle(Envelope $envelope, StackInterface $stack): Envelope | ||
{ | ||
// ignore the dispatched messages for retry | ||
if (null !== $envelope->last(ReceivedStamp::class)) { | ||
$amqpReceivedStamp = $envelope->last(AmqpReceivedStamp::class); | ||
|
||
if ($amqpReceivedStamp instanceof AmqpReceivedStamp && $amqpReceivedStamp->getAmqpEnvelope()->isRedelivery()) { | ||
throw new RejectRedeliveredMessageException('Redelivered message from AMQP detected that will be rejected and trigger the retry logic.'); | ||
} | ||
} | ||
|
||
return $stack->next()->handle($envelope, $stack); | ||
} | ||
} |
Original file line number | Diff line number | Diff line change | ||
---|---|---|---|---|
|
@@ -18,6 +18,7 @@ | |||
use Symfony\Component\Messenger\Event\WorkerMessageReceivedEvent; | ||||
use Symfony\Component\Messenger\Event\WorkerStoppedEvent; | ||||
use Symfony\Component\Messenger\Exception\HandlerFailedException; | ||||
use Symfony\Component\Messenger\Exception\RejectRedeliveredMessageException; | ||||
use Symfony\Component\Messenger\Exception\UnrecoverableExceptionInterface; | ||||
use Symfony\Component\Messenger\Retry\RetryStrategyInterface; | ||||
use Symfony\Component\Messenger\Stamp\DelayStamp; | ||||
|
@@ -135,6 +136,13 @@ private function handleMessage(Envelope $envelope, ReceiverInterface $receiver, | |||
try { | ||||
$envelope = $this->bus->dispatch($envelope->with(new ReceivedStamp($transportName))); | ||||
} catch (\Throwable $throwable) { | ||||
$rejectFirst = $throwable instanceof RejectRedeliveredMessageException; | ||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It seems to me that the BIG important thing here is: if a message is redelivered, don't actually try to handle it again (because it'll probably timeout again). Instead, skip handling and have it be redelivered. Question then: to fix this bug, is it actually important to reject this message before sending the redelivery? If we manage to skip the AMQP-redelivered message from being handled, isn't it ok if we follow the normal messenger-redelivery logic (redeliver the message and then reject it)? Or am I missing something? If rejecting it first is not actually important, we could simplify this patch considerably. thx :) There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Rejecting redelivered messages first is important. As I described in #32055 (comment) and #34082, the repeating errors can happen inside the listeners or the retry publishing (anywhere inside the catch block). In this case, the message never gets rejected (as the exception happens before) and would be redelivered forever. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. See also comment two lines below There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Hmm, ok. To make it feel like less of a one-off solution, wdyt about a RejectMessageImmediatelyExceptionInterface that we actually look for (then the class implements this)? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We only want to reject redelivered messages first and not others to prevent potential loss of messages. So the interface would suggest something we don't want to promote. Also the
|
||||
if ($rejectFirst) { | ||||
// redelivered messages are rejected first so that continuous failures in an event listener or while | ||||
// publishing for retry does not cause infinite redelivery loops | ||||
$receiver->reject($envelope); | ||||
} | ||||
|
||||
if ($throwable instanceof HandlerFailedException) { | ||||
$envelope = $throwable->getEnvelope(); | ||||
} | ||||
|
@@ -156,15 +164,15 @@ private function handleMessage(Envelope $envelope, ReceiverInterface $receiver, | |||
->with(new RedeliveryStamp($retryCount, $transportName)) | ||||
->withoutAll(ReceivedStamp::class); | ||||
|
||||
// re-send the message | ||||
// re-send the message for retry | ||||
$this->bus->dispatch($retryEnvelope); | ||||
// acknowledge the previous message has received | ||||
$receiver->ack($envelope); | ||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I changed this to There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. that seems reasonable. |
||||
} else { | ||||
if (null !== $this->logger) { | ||||
$this->logger->critical('Error thrown while handling message {class}. Removing from transport after {retryCount} retries. Error: "{error}"', $context + ['retryCount' => $retryCount, 'error' => $throwable->getMessage(), 'exception' => $throwable]); | ||||
} | ||||
} | ||||
|
||||
if (!$rejectFirst) { | ||||
$receiver->reject($envelope); | ||||
} | ||||
|
||||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wish there were a way to only run this if at least one Amqp transport were configured, but I know that’s not possible (so not a blocker or real feedback). It makes me wish each transport was actually its own package...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As I said in #34107 (comment), we might want to enhance the middleware later to handle other transports like doctrine.