[ 
https://issues.apache.org/jira/browse/CAMEL-13121?focusedWorklogId=319556&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-319556
 ]

ASF GitHub Bot logged work on CAMEL-13121:
------------------------------------------

                Author: ASF GitHub Bot
            Created on: 27/Sep/19 13:46
            Start Date: 27/Sep/19 13:46
    Worklog Time Spent: 10m 
      Work Description: oscerd commented on pull request #3204: [CAMEL-13121] 
Route irc->irc cycles the message because of irc.target…
URL: https://github.com/apache/camel/pull/3204
 
 
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 319556)
    Time Spent: 40m  (was: 0.5h)

> 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: Minor
>             Fix For: 3.0.0, 2.25.0, 3.0.0.RC2
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> 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
(v8.3.4#803005)

Reply via email to