When I do this:
exception(java.net.SocketException.class)
.maximumRedeliveries(2).useExponentialBackOff().initialRedeliveryDelay(30000).backOffMultiplier(2.0)
.to("jbi:service:http://servicemix.in2m.com/samples/http/bean15Service";);
from("jbi:service:http://servicemix.in2m.com/samples/http/jmsConsumer";)
.setHeader("path", constant("dir"))
.to("jbi:service:http://servicemix.in2m.com/samples/http/MyProviderService?mep=in-out";)
.setHeader("portal", constant("portal"))
.to("jbi:service:http://servicemix.in2m.com/samples/http/PortalService?mep=in-out";);
The flow is like this:
1)message <request>hhh</request> goes to providerservice
2)provider service returns the <response>kkk</response> message
3)As portal service service is down, message is sent to bean15 service. here
the message is <response>kkk</response> and I get two properties:
path=dir and portal=portal
--
View this message in context:
http://www.nabble.com/error-handling-problem-tp18397098s22882p18404302.html
Sent from the Camel - Users mailing list archive at Nabble.com.
