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
