[rabbitmq-discuss] Dead Letter, TTL and Cycle

[Simon MacMullen]

At the moment you would have to consume and republish to purge the 
header outside of RabbitMQ.

In a future release we might relax the no-cycle requirement.

Cheers, Simon

On 12/04/13 10:04, Michaël OULLION wrote:
> Hello,
>
> I work on a solution to consume Message on queue and I use "Dead letter" mechanism.
> I try to distingish 2 type of error when consuming message :
> * Functional
> the message cannot be proceed by the application due to a format bug, We can't requeue it because they won't be proceed.
> * Technical
> The message cannot be proceed because the DB is offline. This kind of message can be proceed when the DB will be back.
>
> So only "technical error"'s message are send to Dead Queue.
> Now, I try to resend "automatically" the message from the Dead Queue to the "live" one.
>
> To do this, I put a TTL parameter on the Queue ( for example 10 minutes), so the message are automatically recycle every 10 minutes.
> This solution work fine... except that I create a cycle ( Live queue => Dead queue => Live Queue) and message are dropped.
>
> Is there a way to "purge" the header of messages when they are recycled directly inside the RabbitMQ Server?
> Or Do I create an specific client to read Dead message, purge header and resend it ?
>
> Regards,
> ___________________________________________________________
> Le spectacle de Franck Dubosc perturbé à cause de Koh-Lanta ! Plus d'explications ici http://people.voila.fr/people/actu-stars/personnalites/franck-dubosc-oblige-de-reecrire-son-spectacle-a-cause-de-koh-lanta-people_9953.html
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>


-- 
Simon MacMullen
RabbitMQ, VMware