[
https://issues.apache.org/jira/browse/CAMEL-18570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17862405#comment-17862405
]
Claus Ibsen commented on CAMEL-18570:
-------------------------------------
In Camel v3 you can call another route that is transacted as follows:
{code}
from("activemq:start")
.transacted("required")
.aggregate(header("id"), new MyAggregationStrategy())
// use our created jdbc repo as aggregation repository
.completionSize(5).aggregationRepository(aggregationRepository)
.to("direct:agg");
from("direct:agg")
.transacted()
.to("activemq:aggregated");
{code}
> Aggregation onCompleted does not open XA transaction
> ----------------------------------------------------
>
> Key: CAMEL-18570
> URL: https://issues.apache.org/jira/browse/CAMEL-18570
> Project: Camel
> Issue Type: Bug
> Components: camel-core, camel-sql
> Affects Versions: 3.18.2
> Reporter: Julien Hattab
> Priority: Minor
> Labels: aggregation, xaresource
> Attachments: camel-v2-xaJdbcAggregation.zip,
> camel-v3-xaJdbcAggregation.zip
>
>
> Since Camel 3 version.
> The aggregation processor doesn't open a XA transaction when the aggregation
> is completed or timed-out.
> If the aggregated route destination is a XA resource camel throw the
> following exception :
> {code:java}
> Session's XAResource has not been enlisted in a distributed transaction {code}
> I create 2 projects with one test.
> One in camel 3.18.2 which is failing and one with camel 2.25.4 which is
> successful.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
