@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 successfully in the customer side. I understand that the HTTP connections are designed to behave this way. However I am concerned that Camel is throwing an exception *and* also processing the output of the producer - this may be an anomaly. 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.
You can look at Rosmon's diff - if we make a small modification, Camel is working exactly like it used to work in 1.x. Anyone else have comments on what Camel should be doing on a read timeout??? According to me if an exception happened within a process then the process is not complete and we should not pass forward the half cooked output of the process. Isn't that a fair assumption? Hari Gangadharan -- View this message in context: http://camel.465427.n5.nabble.com/Http-route-returning-with-200-but-also-getting-read-timed-out-tp3741631p3895320.html Sent from the Camel - Users mailing list archive at Nabble.com.
