activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Strachan" <james.strac...@gmail.com>
Subject Re: Asynch errors sending transacted messages to 4.1
Date Tue, 06 Mar 2007 09:49:42 GMT
On 3/5/07, John Toohey <jt@parspro.com> wrote:
> Hi,
>
> My app is using a single-resource transaction to process messages
> from a persistent queue. I read the messages in a transaction,
> process the data, and commit the transaction on success. If my
> business logic fails, I roll-back the transaction. When the message
> gets re-delivered, I try one more time. If it fails again, I send a
> copy of the message to another persistent queue for off-line
> processing, and then commit the original message, to remove it from
> the queue.

FWIW ActiveMQ already supports dead letter queues for exactly this purpose.


> However, under the load of about 100 messages, I get the following
> from the message broker :-

Unfortunately I don't understand what the Mule codebase is doing so I
can't really help much more I'm afraid. Maybe try the Mule lists?


-- 

James
-------
http://radio.weblogs.com/0112098/

Mime
View raw message