Hi

Ah yeah so you are doing something like

from breanstalk a
to beanstalk b

and then it goes to a instead?

Ye had similar issue with rabbitmq I think. You are welcome to log a
JIRA ticket (issue tracker)
http://camel.apache.org/support.html

On Thu, Jan 28, 2016 at 5:48 PM, J.R. Smith <[email protected]> wrote:
> The Apache Camel Beanstalk component appears to be broken when a route
> consumes AND produces to a beanstalk endpoint (with different tubes). It
> seems as if the headers from the consumption exchange get used when trying
> to produce to the endpoint (I think).
>
> J



-- 
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Reply via email to