I created a ticket. Just FYI I tried to mark the component in the ticket but Apache Camel Beanstalk is not available for selection in the list. Thank you.
On Fri, Jan 29, 2016 at 2:58 AM, Claus Ibsen <[email protected]> wrote: > 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 > -- *J.R. Smith* *Software Developer* Main 972.546.3878 <https://www-staging.geoforce.net/uploads/downloads/esignature.html> Fax 972.546.3871 <https://www-staging.geoforce.net/uploads/downloads/esignature.html> Toll Free 888.574.3878 <https://www-staging.geoforce.net/uploads/downloads/esignature.html> *Geoforce.com* <http://www.geoforce.com/> *Geoforce *750 Canyon Dr. Suite 140 Coppell, Texas 75019 <https://www.facebook.com/geoforceinc> <https://twitter.com/geoforce> <https://www.linkedin.com/company/geoforce-inc> <https://instagram.com/geoforce_tracking/> <https://oilpro.com/company/152135/geoforce> *CONFIDENTIAL* - If you are not the intended recipient, please delete this message without disclosing it.
