Hi, Have you tried increasing the producers timeout window and introducing keep-alives on the connection
Can you add the option httpClient.soTimeout=20000 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 a HTTP Connection timeout is not a bug in Camel. This is how HTTP connections are designed to behave. The best you can do is to set the connection timeout to a higher value. Also not sure what you are trying to do here, but trying to re-deliver a message to a slow consumer can cause duplicate message sent to the consumer and have the opposite effect where he get loaded now with redundant requests. If the consumer is just slow and did not get back in time for the connection window to be closed does not mean he did not process the message. You will need to further configure your HTTP Producer to deal with the scenario at hand. If on the other hand it is a true exception other than a timeout, there is obviously no point in retrying. Hope this helps. Cheers, Ashwin... ----- --------------------------------------------------------- Ashwin Karpe Apache Camel Committer & Sr Principal Consultant FUSESource (a Progress Software Corporation subsidiary) http://fusesource.com Blog: http://opensourceknowledge.blogspot.com --------------------------------------------------------- -- View this message in context: http://camel.465427.n5.nabble.com/Http-route-returning-with-200-but-also-getting-read-timed-out-tp3741631p3893697.html Sent from the Camel - Users mailing list archive at Nabble.com.
