[
https://issues.apache.org/jira/browse/CAMEL-17474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498151#comment-17498151
]
Zheng Feng edited comment on CAMEL-17474 at 2/25/22, 3:21 PM:
--------------------------------------------------------------
[~jeremyross] [~jondruse] I just found that if adding "transacted()" in route2,
it works.
{code:java}
from("direct:route2").routeId("r.route2")
.log(LoggingLevel.DEBUG, "Entering route: ${routeId}")
.transacted()
.multicast()
// 2 or more multicast children will deadlock after the last
child
.to("log:r.test", "direct:route3")
.end();
{code}
So it looks like the exchange in the sub-routes is not trancated ?
was (Author: zhfeng):
[~jeremyross][~jondruse] I just found that if adding "transacted()" in route2,
it works.
{code:java}
from("direct:route2").routeId("r.route2")
.log(LoggingLevel.DEBUG, "Entering route: ${routeId}")
.transacted()
.multicast()
// 2 or more multicast children will deadlock after the last
child
.to("log:r.test", "direct:route3")
.end();
{code}
> camel-core: deadlock with multicast in a transacted context
> -----------------------------------------------------------
>
> Key: CAMEL-17474
> URL: https://issues.apache.org/jira/browse/CAMEL-17474
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 3.13.0, 3.14.0
> Reporter: Jeremy Ross
> Assignee: Jiri Ondrusek
> Priority: Major
> Fix For: 3.14.2, 3.16.0
>
>
> Using a multicast with more than one child in a transacted context causes a
> deadlock. Reproducer here
> https://github.com/jeremyross/camel-transacted-multicast.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
