Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Message-ID: <1372308183.1259849394138.JavaMail.jira@brutus>
Date: Thu, 3 Dec 2009 06:09:54 -0800 (PST)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: camel-dev@activemq.apache.org
Subject: [jira] Commented: (CAMEL-2254) TransactionErrorHandler - Better
 support for mixed transactions using different propagation behaviors
In-Reply-To: <150068341.1259843632760.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/activemq/browse/CAMEL-2254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56246#action_56246 ] 

Claus Ibsen commented on CAMEL-2254:
------------------------------------

trunk: 886781.

And at DEBUG level you can see the transaction begin/commit/rollback events. For example here we got an outer and inner TX where its the inner that rollback while the outer commits.
{code}
2009-12-03 15:08:28,793 [main           ] DEBUG TransactionErrorHandler        - Transaction begin (0x2bed82) for ExchangeId: 8e034445-a6ad-4504-8a1a-1cebe129cee4
2009-12-03 15:08:29,884 [main           ] DEBUG TransactionErrorHandler        - Transaction begin (0x967db7) for ExchangeId: 8e034445-a6ad-4504-8a1a-1cebe129cee4
2009-12-03 15:08:29,886 [main           ] DEBUG TransactionErrorHandler        - Transaction rollback (0x967db7) for ExchangeId: 8e034445-a6ad-4504-8a1a-1cebe129cee4
2009-12-03 15:08:29,887 [main           ] DEBUG TransactionErrorHandler        - Transaction commit (0x2bed82) for ExchangeId: 8e034445-a6ad-4504-8a1a-1cebe129cee4
{code}

> TransactionErrorHandler - Better support for mixed transactions using different propagation behaviors
> -----------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-2254
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2254
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core, camel-spring
>    Affects Versions: 2.0.0, 2.1.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.2.0
>
>
> So you can have multiple routes with different transaction propagations
> route a - required
> route b - requires new
> Then let a message route a -> b.
> And in case b should rollback then a can still be comitted
> But also the entire route should be able to rollback
> And hence why we need to introduce a new keyword {{markRollbackLocalOnly()}} in the DSL which can be used to say that in case route B fails then just rollback this route but the outer transaction should still be comitted.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.