I would like to know how others would address the following use case: It is about jms to http communication. Requirement is if we get ConnectException or http response code 503 then we should keep on retrying the delivery.
However if we get anything else apart from 200 and 503 as response code we just need to rollback the message. I tried doing it as follows which works nicely. However if exchange gets connect exception first and then 500 on redelivery, it stll keeps on redelivering forever as if it has still got ConnectException. Looks like it goes by the very first exception that it had encountered. Any thought around how to deal with this? -- View this message in context: http://camel.465427.n5.nabble.com/Exception-Handling-using-onException-tp5711863.html Sent from the Camel - Users mailing list archive at Nabble.com.
