Hi,
I merged the test to Camel 1.x branch, the test looks good.
Can you try to use the latest released Camel 1.6.1?
Willem
Claus Ibsen wrote:
> Hi
>
> I created a unit test with the tineout.
>
> You can check it out by this link:
> http://svn.apache.org/viewvc?view=rev&revision=781775
>
> It
Hi
I created a unit test with the tineout.
You can check it out by this link:
http://svn.apache.org/viewvc?view=rev&revision=781775
It uses Camel trunk however. But see if that works for your version of Camel.
On Thu, Jun 4, 2009 at 5:06 PM, LeRoy Michel wrote:
> Hi,
> I confirm that the SO_
Hi,
I confirm that the SO_TIMEOUT is the right property to set for timeout
connection. The code below works with http client API :
-
HttpClient client = new HttpClient();
PostMethod method = new PostMethod("http://localhost:8080/MyResource";);
client.getParams().setParameter(HttpMethodParam
Hi
Try getting the timeout to work directly using HTTP client API. Then
you know which settings work.
Then setting the same option with the Camel URI should do the same.
But maybe there is a gremlin in the code.
On Thu, Jun 4, 2009 at 10:11 AM, LeRoy Michel wrote:
> Hi,
>
> I've tested http r
Hi,
I've tested http request with the following URI :
"
http://localhost:8080/myResource?httpClient.soTimeout=10&httpClient.connectionManagerTimeout=20
"
Even if I change the value of httpClient.soTimeout and
httpClient.connectionManagerTimeout parameters, the response time of server
doesn't cha
Hi,
The last one which sets the httpClient's parameter in the URI should work.
I checked the HttpClientParams java doc, there is no properties of
connectionTimeout, I think you need to try to use
connectionManagerTimeout instead of connectionTimeout.
BTW, In Camel 2.0, we have the parameter valid
