[
https://issues.apache.org/jira/browse/CAMEL-13121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16752148#comment-16752148
]
Claus Ibsen commented on CAMEL-13121:
-------------------------------------
Some of the other components did that too, and the workaround was to remove
that header. The solution is to use another named header for overriding the
target in the producer, and not use the name of the header from the consumer.
> Route irc->irc cycles the message because of "irc.target" header
> ----------------------------------------------------------------
>
> Key: CAMEL-13121
> URL: https://issues.apache.org/jira/browse/CAMEL-13121
> Project: Camel
> Issue Type: Bug
> Components: camel-irc
> Affects Versions: 2.21.0
> Reporter: Radovan Netuka
> Assignee: Dmitry Volodin
> Priority: Major
>
> Configure this route:
> from("irc://priv@localhost:6667/test1")
> .log("${headers}")
> .to("irc://chan@localhost:6667/test2");
>
> Send private message to user _priv._
>
> Expected result:
> The message is routed to user _chan._
>
> Actual result:
> The message is routed back to user _priv_ and enters an infinite loop
>
> Cause:
> Inside camel-core Pipeline, the IRC message has still its old target set in
> its properties.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
