Hi ,
Current HTTP producer will not retry if the response is 401/404/500.
It just put the response back in the fault message body and it will not
trigger the default error handler[1] for retring.
Your application code should call exchang.isFailed() for checking the
fault response.
For the Camel 1.5 , we are planing to cut a RC next week. I don't think
camel-http 1.5-SNAPSHOT can work with camel-core 1.4, since they are
some change between the core and http component in Camel 1.5.
We are publishing the snapshot every day here[2], please take a try :)
[1] http://activemq.apache.org/camel/error-handler.html
[2] http://people.apache.org/repo/m2-snapshot-repository
Willem
harinair wrote:
Willem:
Thanks a lot for the quick reply. So you mean to say that the latest
SNAPSHOT will mark response != 200 as failed - right? I guess, that also
means there will be retries by HTTP producer for 500 / 401/ 404 etc.
If that is the case then it is great. When is the 1.5 release planned? I am
planning to go live this week for a small project and I uncovered this bug
on a test. Is 1.5 fairly stable? Or is it recommended that I use just the
camel-http component from the 1.5-SNAPSHOT?
Regards,
Hari Gangadharan
willem.jiang wrote:
I just did a fixe on CAMEL-807[1] which relates your issue.
Now we will put the response into the fault message if the response is
not 200.
You can know it when you call the exchange.isfailed().
Please check out the latest snapshot and feel free to add your feed back.
[1]https://issues.apache.org/activemq/browse/CAMEL-807
Willem
