Hi If you want to keep the bad message in the original queue, then you are also blocking the messages that has arrived on the queue after the bad message.
By default Camel will retry consuming a message up til 6 times before its moved to the default dead letter queue. If you configure the dead letter channel to use maximumRedeliveries = -1 then Camel will retry forever. http://activemq.apache.org/camel/dead-letter-channel.html When you consume a message you can check the in message header "org.apache.camel.redeliveryCount" that contains the number of times it has been redlivered. Or "org.apache.camel.Redelivered" that contains a boolean if its redelivered or if its the first time the message is processed. Med venlig hilsen Claus Ibsen ...................................... Silverbullet Skovsgårdsvænget 21 8362 Hørning Tlf. +45 2962 7576 Web: www.silverbullet.dk -----Original Message----- From: pevgen [mailto:[EMAIL PROTECTED] Sent: 9. juni 2008 15:49 To: [email protected] Subject: send a notification and keep the bad message in the queue Hi. I use activeMQ endpoints. I want to send a notification to admin and keep the bad message in the queue. because when admin will repair the broken to-endpoint, the message must try to send again. Can I do it ? thanks Evgeny -- View this message in context: http://www.nabble.com/send-a-notification-and-keep-the-bad-message-in-the-queue-tp17733224s22882p17733224.html Sent from the Camel - Users mailing list archive at Nabble.com.
