Thank you to both! On Thu, Aug 18, 2011 at 2:57 AM, Dejan Bosanac <de...@nighttale.net> wrote:
> Also take a look at this article > > http://activemq.apache.org/message-redelivery-and-dlq-handling.html > > Regards > -- > Dejan Bosanac - http://twitter.com/dejanb > ----------------- > The experts in open source integration and messaging - > http://fusesource.com > ActiveMQ in Action - http://www.manning.com/snyder/ > Blog - http://www.nighttale.net > > > On Wed, Aug 17, 2011 at 8:38 PM, Hervé BARRAULT <herve.barra...@gmail.com > >wrote: > > > HI, > > if you are using Enterprise Integration Patterns, you can use the > > DeadLetterChannel Pattern : > > http://www.enterpriseintegrationpatterns.com/DeadLetterChannel.html > > Regards > > > > 2011/8/17 Walter Closenfleight <walter.p.closenflei...@gmail.com> > > > > > I'm confused on how to deal with failures. > > > > > > If any part of my logic in the processMsg (below) fails (external > > resources > > > not available, wrong parameters passed in queueMsg, etc.) then I do not > > > want > > > the message to be dequeued. I realize, however, that the message will > > then > > > just fire again and keep failing. So, how do I deal with failures? If > the > > > message in the queueMsg is important and I don't want to lose its data, > > how > > > can I prevent that from happening? Perhaps I could bundle the queueMsg > > into > > > a failures area on my machine and analyze them programmatically or by > > hand > > > at a later time. > > > > > > > > > @Async > > > > > > *public* *void* processMsg(QueueMessage queueMsg) { > > > > > > // check if database available, if not, put this message back on queue > > or > > > store somewhere > > > > > > } > > > > > > Cheers! > > > > > >
