Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (nike.apache.org: domain of
 walter.p.closenfleight@gmail.com designates 74.125.83.43 as permitted sender)
MIME-Version: 1.0
Date: Wed, 17 Aug 2011 12:54:01 -0500
Message-ID: 
 <CAOO+EWQg05e5811YPK+evHP4VoYZMNoE00LFt9TB46rsVRK3cA@mail.gmail.com>
Subject: How to deal with failures on a queue
From: Walter Closenfleight <walter.p.closenfleight@gmail.com>
To: users@activemq.apache.org
Content-Type: multipart/alternative; boundary=000e0cd293c270b96c04aab72e09

--000e0cd293c270b96c04aab72e09
Content-Type: text/plain; charset=ISO-8859-1

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!

--000e0cd293c270b96c04aab72e09--