camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <claus.ib...@gmail.com>
Subject Re: Dropped jms messages on java.io.UTFDataFormatException
Date Tue, 04 Aug 2009 17:40:25 GMT
Try using AMQ redeliver handling and its DLQ
http://activemq.apache.org/message-redelivery-and-dlq-handling.html
http://activemq.apache.org/redelivery-policy.html

Then when you message fails X number of times AMQ should be able to
move it to a DLQ



On Tue, Aug 4, 2009 at 6:05 PM, Ensonik<mike.mclean@streamtheworld.com> wrote:
>
> Actually, I'm struggling to understand what you're suggesting. All my JMS
> interaction is done through Camel right now. I need to hook and get access
> to that message outside of Camel ...
>
> So if I get it right, I'll need to have some sort of consumer (which doesn't
> use Camel) on my queue which will check the payload, then once it's
> confirmed as right, move to a queue where Camel is listening?
>
> Do you see the irony? I'm guessing that it's not what you're suggesting, but
> right now, that's all I can see. Dropping messages is not an option for me
> (as I'm guessing is the case for many).
>
>
> Claus Ibsen-2 wrote:
>>
>> On Mon, Aug 3, 2009 at 4:16 AM, Willem Jiang<willem.jiang@gmail.com>
>> wrote:
>> Yes the Camel error handling is based on message exchanges and not on
>> initial transport issues.
>>
>> You can / should remedy this with AMQ as its has a poison message. And
>> must have means to be able to deal with it in AMQ.
>>
>
> --
> View this message in context: http://www.nabble.com/Dropped-jms-messages-on-java.io.UTFDataFormatException-tp24761350p24811480.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>



-- 
Claus Ibsen
Apache Camel Committer

Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus

Mime
View raw message