Return-Path: X-Original-To: apmail-camel-issues-archive@minotaur.apache.org Delivered-To: apmail-camel-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0366217A8F for ; Sat, 30 Jan 2016 20:25:40 +0000 (UTC) Received: (qmail 47431 invoked by uid 500); 30 Jan 2016 20:25:39 -0000 Delivered-To: apmail-camel-issues-archive@camel.apache.org Received: (qmail 47394 invoked by uid 500); 30 Jan 2016 20:25:39 -0000 Mailing-List: contact issues-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list issues@camel.apache.org Received: (qmail 47385 invoked by uid 99); 30 Jan 2016 20:25:39 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 30 Jan 2016 20:25:39 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id BF2EB2C0AFA for ; Sat, 30 Jan 2016 20:25:39 +0000 (UTC) Date: Sat, 30 Jan 2016 20:25:39 +0000 (UTC) From: "J Smith (JIRA)" To: issues@camel.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CAMEL-9552) Cannot consume and produce to beanstalk component in the same route MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 J Smith created CAMEL-9552: ------------------------------ Summary: Cannot consume and produce to beanstalk component in the same route Key: CAMEL-9552 URL: https://issues.apache.org/jira/browse/CAMEL-9552 Project: Camel Issue Type: Bug Affects Versions: 2.16.0, 2.15.0 Reporter: J Smith It appears that when creating a route that consumes from one beanstalk tube and produces to another, the exchange headers from the consumer somehow get mixed in with the producer and cause errors. Example route: .from("beanstalk://localhost?tube=A") .setBody("hello") .to("beanstalk://localhost?tube=B") -- This message was sent by Atlassian JIRA (v6.3.4#6332)