- Notifications
You must be signed in to change notification settings - Fork464
How to handle error messages without ACK nor infinite retry#630
-
Hi everyone, This is my current rabbtimq configuration old_sound_rabbit_mq:producers:# only here for dead-letter exchange pattern, do not use directlylambda:connection:defaultexchange_options:{name: lambda_ex, type: direct}consumers:lambda:connection:defaultexchange_options:{name: gamma_ex, type: fanout }# or directqueue_options:name:lambda_qarguments:'x-dead-letter-exchange':[S, lambda_on_error_ex]'x-dead-letter-routing-key':[S, '']callback:app.consumer.lambda_consumer# only here for dead-letter exchange pattern, do not use directlylambda_on_error:connection:defaultexchange_options:{name: lambda_on_error_ex, type: direct}queue_options:name:lambda_on_error_qarguments:'x-dead-letter-exchange':[S, lambda_ex]'x-message-ttl':['I', 10000]callback:app.consumer.lambda_consumer# wont be used but the key must be present :/bindings: -{exchange: lambda_ex, destination: lambda_q} In my Instead of losing the message, I want to save it "somewhere" and be able to retry when the third party server comes back on. Is there a simple way to do it with RabbitMq ? I was thinking of
But I can't find a suitable way to start the consumer asynchronously within Symfony app... Thank you for your help, Yannick |
BetaWas this translation helpful?Give feedback.
All reactions
Replies: 0 comments
This discussion was converted from issue #570 on March 26, 2021 10:39.