Mailing-List: contact activemq-users-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: activemq-users@geronimo.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Message-ID: <44AFEE48.3020906@ldsys.net>
Date: Sat, 08 Jul 2006 12:41:28 -0500
From: "Christopher G. Stach II" <cgs@ldsys.net>
User-Agent: Thunderbird 1.5.0.4 (X11/20060603)
MIME-Version: 1.0
To: activemq-users@geronimo.apache.org
Subject: Re: ActiveMQ 4 + Jencks + XA Transactions
References: <5196977.post@talk.nabble.com>
 <ec6e67fd0607060816h745e31acqd2496e47f7f39a4b@mail.gmail.com>
 <5213459.post@talk.nabble.com>
 <ec6e67fd0607070137q5abeb3dayb46d6244cd43001a@mail.gmail.com>
 <5217720.post@talk.nabble.com>
In-Reply-To: <5217720.post@talk.nabble.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Johan Brelet wrote:
> Perhaps I said a bit too fast that it was working fine... :)
> 
> Here is the problem I have now :
> In my tests I try to force the broker to rollback a global XA transaction
> when receiving a JMS Message. To do that, the onMessage() method throws a
> RuntimeException. So, I expect the broker to catch this exception, and then
> to rollback transaction, and later to try again delivering the message.
> But with ActiveMQ4.1 and latest Jencks from SVN HEAD, I don't understand the
> behaviour of the broker... The exception doesn't cause the transaction to
> rollback, so it stays active, and the broker do not redeliver the message.
> Here is a part of logs :
[...]
> I don't really understand what's going on...Am I doing something wrong ? Or
> is it a problem with ActiveMQ 4.1 ?

According to the spec, onMessage should not throw RuntimeException.  Get
a handle on the current Transaction and setRollbackOnly().

-- 
Christopher G. Stach II