Handling ActiveMQ disconnects in Camel CXF Routes: Part 2
But what if we need ActiveMQ to be asynchronous? Seems easy, just change the exchange pattern to be InOnly for the ActiveMQ call like so:
.inOnly("activemq:queue.test")So now your route returns much faster since it is not waiting on a reply from the ActiveMQ endpoint. Cue the angels....... but wait, what happens when we still need the error handling to catch the JMSException and return a predefined response if..... lets say.... ActiveMQ is down?
With the ExchangePattern set to InOnly, you will see in SOAPUI that you just get an empty soap message. So what happened to the predefined response? If you have logging in you processor or bean that loads the response, you will see that it is still hitting your code, but it is not return the response for some reason.
THE REASON: The reason is you have an ExchangePattern of InOnly set when you run the onException code, this is causing the camel route to return before your processor is finished processing. So your exception processing does not effect the return to the CXF endpoint.
THE SOLUTION: you need to specify the onException portion of your route to be InOut using the following:
.onException(Exception.class).handle(true).setExchangePattern(ExchangePattern.InOut).processRef(myProcessor)Now you should see your processor defined response from the onException getting passed back to the endpoint.
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)