Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Thu, 17 Mar 2011 19:47:29 +0000 (UTC)
From: "Ashwin Karpe (JIRA)" <jira@apache.org>
To: dev@camel.apache.org
Message-ID: 
 <927794885.9839.1300391249527.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Created: (CAMEL-3788) HTTP Producer seems to send an empty
 body request on redelivery when the original request fails due to a
 connection timeout
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

HTTP Producer seems to send an empty body request on redelivery when the original request fails due to a connection timeout
---------------------------------------------------------------------------------------------------------------------------

                 Key: CAMEL-3788
                 URL: https://issues.apache.org/jira/browse/CAMEL-3788
             Project: Camel
          Issue Type: Bug
          Components: camel-http
    Affects Versions: 2.6.0, 2.0-M2
            Reporter: Ashwin Karpe


Camel HTTP Producer is throwing an exception when it encounters a connection timeout. However instead of preserving the original message it is treating it processing the exception output. When connected to a redelivery meachanism, this results in an exception message being sent as input to the HTTP Consumer. The older versions of Camel behaved differently on read timeout. In Camel 1.x, in a read timeout, the Exception is thrown and the input message to the producer is passed through the pipeline. Now there is a difference: An exception is thrown and the output of the HTTP Producer is passed through the pipeline. 

Need to study why and what changed since Camel 1.x and ensure that the above does not happen.

For more details, please check out the following nabble entry

http://camel.465427.n5.nabble.com/Http-route-returning-with-200-but-also-getting-read-timed-out-td3741631.html#a3897410

Cheers,

Ashwin...

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira