Hi Hari,
I can reproduce the error by writing a simple unit test.
I just create a JIRA[1] for it, will commit short fix for this case.
[1]https://issues.apache.org/jira/browse/CAMEL-3792
Willem
On 3/19/11 2:12 AM, Hari Gangadharan wrote:
Willem:
We have tried everything. We were already sett
Willem:
We have tried everything. We were already setting useOriginalMessage=true.
Here is the route:
java.lang.Exception
true
On 3/18/11 3:00 AM, Hari Gangadharan wrote:
@Ashwin:
We have looked at that consumer - they are too slow and it is the consumer's
fault. Even if we increase the timeout to 20 sec, there would be another
consumer that will have the same issue. My spec is to wait only 10 sec. I
will try to redeliv
Hi
I know what's you mean after checking out the patch that you provided.
Current camel http code just assume that there is a response, and create
a null message after exchange.getOut is called.
You change just make sure the exchange.getOut() will not be called if
the Timeout exception is thr
Add a Jira entry in Camel. Please see link below
https://issues.apache.org/jira/browse/CAMEL-3788
Cheers,
Ashwin...
-
-
Ashwin Karpe
Apache Camel Committer & Sr Principal Consultant
FUSESource (a Progress Software Corporation subsidiar
Ah ok... Yep this behavior may be a bug.
I will try and create a Jira issue for this problem and link it back to this
issue for you to track and us to correct. BTW, can you please send me the
exact error that is being thrown. I will also check out version 1.0 to see
what was different.
Cheers,
@Ashwin:
We have looked at that consumer - they are too slow and it is the consumer's
fault. Even if we increase the timeout to 20 sec, there would be another
consumer that will have the same issue. My spec is to wait only 10 sec. I
will try to redeliver until I am sure that it is processed succes
Hi,
Have you tried increasing the producers timeout window and introducing
keep-alives on the connection
Can you add the option httpClient.soTimeout=2 to your HTTP Producer and
see if the producer hangs around for 20 seconds.
BTW, the fact that the HTTP client bails after a fixed period for
@Willem:
We have found that this issue can be fixed by making a change to the
HttpProducer.java class.
The issue is that we're extracting the body after calling the
"exchange.getOut()".
This means that if there's an exception while extracting the body the
original message will not get sent to the
@Willem:
We will not be able to make server respond faster since it is customer's
server. I believe there is a bug in Camel framework. In this scenario, the
HTTP Producer thinks that the exchange has completed successfully whereas
the Camel framework thinks that the exchange has failed. Camel fra
Hi,
From the log I can see the http client get the 200 http response, but
the connection is closed after 10 seconds
Just checked the HttpProducer code it will call
InputStream is = method.getResponseBodyAsStream();
to get the response, it looks like the server can't return any data in
the 10
11 matches
Mail list logo
