[
https://issues.apache.org/jira/browse/CAMEL-17474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479137#comment-17479137
]
Jiri Ondrusek edited comment on CAMEL-17474 at 1/20/22, 7:29 AM:
-----------------------------------------------------------------
[~jeremyross] You are right, it doesn't help top have different endpoints. (I
probably simulated that case with the working camel version - so it showed
false success).
*But the origin of the reason is still the same as I wrote*.
Now I don't think that it is the right behavior. Deadlock is an issue, which
shouldn't be there. Following route shouldn't cause deadlock, but it causes.
{code}
.multicast()
.to("log:r.test", "direct:r.test")
.end();
{code}
was (Author: jondruse):
[~jeremyross] You are right, it doesn't help top have different endpoints. (I
probably simulated that with working camel version).
But the origin of the reason is still the same as I wrote.
Bow I don't think that it is the right behavior, it doesn't make sense to
deadlock for example
{code}
.multicast()
.to("log:r.test", "direct:r.test")
.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
>
> 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)
