camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bocamel <>
Subject DirectVmConsumerNotAvailableException cannot be caught by onException?
Date Wed, 16 Dec 2015 17:08:40 GMT
I have the following context level OnException.  After it catches an error,
it would send out an email alert using a direct-vm route.  But to avoid
infinite loop, the email alert is only sent if the OnException is not
entered due to a nested exception.

When the direct-vm consumer is not started and there is an exception (e.g.
ValidationException), the OnException is entered and then fail with
which is expected.  I had expected that the
DirectVmConsumerNotAvailableException is caught by the OnException again.
But it was not. I need to catch it so that the original ValidationException
can be "handled".  Any suggestion?


		<c:when><c:groovy> !=
 		    <c:setProperty propertyName="eb_already_in_recovery">            
	            <c:setExchangePattern pattern="InOnly" />
        	    <c:to uri="direct-vm:sendEmailAlert" />
			<c:log message="***** Failed again in error recovery:

View this message in context:
Sent from the Camel - Users mailing list archive at

View raw message