activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hervé BARRAULT <herve.barra...@gmail.com>
Subject Re: How to deal with failures on a queue
Date Wed, 17 Aug 2011 18:38:53 GMT
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.closenfleight@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!
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message