Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Wed, 30 Oct 2013 09:32:25 +0000 (UTC)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <JIRA.12664658.1377022480757.4156.1383125545560@arcas>
In-Reply-To: <JIRA.12664658.1377022480757@arcas>
References: <JIRA.12664658.1377022480757@arcas>
Subject: [jira] [Commented] (AMQ-4687) Rar losing messages when there is a
 XA trx timeout (jboss)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/AMQ-4687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13808887#comment-13808887 ] 

Claus Ibsen commented on AMQ-4687:
----------------------------------

Have you tried with AMQ 5.9. There has been some improvements/fixes in the RAR and XA.

> Rar losing messages when there is a XA trx timeout (jboss) 
> -----------------------------------------------------------
>
>                 Key: AMQ-4687
>                 URL: https://issues.apache.org/jira/browse/AMQ-4687
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.6.0
>         Environment: Jboss 6.0.1, JDK 1.6, ActiveMQ 5.6
>            Reporter: Juan Manuel Lopez
>            Priority: Critical
>             Fix For: 5.x
>
>
> ActiveMQ does a trx commit when there is a transaction timeout (EJBTransactionRolledbackException). In this way we are losing messages when there is any timeout.
> We have seen that the activemq connections are enlist in XA.
> The attribute transactionContext from ActiveMQSession class has the global transaction reference (xid) before calling the MDB (messageListener.onMessage(message)).
> When the timeout is reached and the RuntimeException is throwned, the transactionContext losed the xid reference.
> Later, when ActiveMQSession call the method transactionContext.isInXATransaction() the result is false because there is no xid reference.
> This situation only happened when the MDB calls other EJB (Stateless) with CMT - TransactionAttributeType.REQUIRES_NEW, and the exception is throwed inside the Stateless.
> I've tried to reproduce this without calling the stateless ejb but it works well.
> The ActiveMQSession class should retain the original transactionContext.
> I found these is the same problem jira https://issues.apache.org/jira/browse/AMQ-4634 but is possible move this fix into version ActiveMQ 5.6 ?
> Regards


--
This message was sent by Atlassian JIRA
(v6.1#6144)