Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: softfail (nike.apache.org: transitioning domain of
 toomanyedwards@gmail.com does not designate 216.139.236.26 as permitted
 sender)
Date: Tue, 21 Jan 2014 08:08:50 -0800 (PST)
From: toomanyedwards <toomanyedwards@gmail.com>
To: users@camel.apache.org
Message-ID: <1390320530416-5746289.post@n5.nabble.com>
Subject: soTimeout ignored by camel http component
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi all,
  We are trying to set the timeout for http client connections.  The http
component docs (http://camel.apache.org/http.html) indicate that we should
be able to set this as a URI param (eg. -
http://foo.com?httpClient.soTimeout=5000), BUT this doesn't work if setting
the URI via the Exchange.HTTP_URI header.  The timeout is completely
ignored.  There's nothing in the http component docs that I have found that
indicate when specifying the URI via the Exchange.HTTP_URI header that the
timeout settings will be ignored.  I found a message thread
(http://camel.465427.n5.nabble.com/setting-http-soTimeout-via-setHeader-is-not-working-td5716218.html)
indicating that you have to use recipient list for timeouts to be respected.
This is definitely counter intuitive and if someone develops a route using
the Exchange.HTTP* headers and then needs to specify a time out they may
need to change in their route logic since the configuration of the recipient
list component is different from the http component.

Is having to use the recipient list component to support client http
timeouts an explicit requirements decision or because of a technical
limitation(s) of the http component?  Is there a way to use the http
component and specify the URI vi the Exchange.HTTP_URI header or is using
recipient list the only way to do it?

Thanks for any feedback.  We have been very happy with using camel in our
project and this is the first thing we've come across that I'd characterize
as a major bug, but hopefully I'm mistaken here.  Thanks again!

-e


--
View this message in context: http://camel.465427.n5.nabble.com/soTimeout-ignored-by-camel-http-component-tp5746289.html
Sent from the Camel - Users mailing list archive at Nabble.com.