[Messenger] [AMQP] Add TransportMessageIdStamp logic for AMQP #59526
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use
TransportMessageIdStamp
for AMQP bridge like Doctrine bridge for example.Implement it in
AmqpSender
asDoctrineSender
(https://github.com/symfony/symfony/blob/7.3/src/Symfony/Component/Messenger/Bridge/Doctrine/Transport/DoctrineSender.php#L51)Implement it in
AmqpReceiver
asDoctrineReceiver
(https://github.com/symfony/symfony/blob/7.3/src/Symfony/Component/Messenger/Bridge/Doctrine/Transport/DoctrineReceiver.php#L148)With this update, logger for AMQP will have more context with
message_id
data (https://github.com/symfony/symfony/blob/7.3/src/Symfony/Component/Messenger/EventListener/SendFailedMessageForRetryListener.php#L55)