Hi Claus,Thanks for your prompt reply. 1)But what is surprising is that
there is no exception trace + the messages stay in processing state forever.
Also, we are not able to stop / undeploy the camel bundles. Also, I see in
QuartzEndpoint.java line no. 123, it logs an exception similar to what we
see in our logs:
LOG.error(CamelExchangeException.createExceptionMessage("Error processing
exchange", exchange, e)); 2) When can this condition happen: ‘Message
exchange stops but no MessageExchangeFailed event is thrown by Camel and our
messages stays in 'PROCESSING' state... 3) Also, this behaviour is not
consistent. In some VM's the routes complete and in some VM's, the messages
stay in processing status..Kindly advise.Thanks,Lakshmi
<http://camel.465427.n5.nabble.com/file/n5751737/camel_NPE.png>
--
View this message in context:
http://camel.465427.n5.nabble.com/Null-Pointer-exception-with-camel-quartz-simple-trigger-fireNow-tp5751692p5751737.html
Sent from the Camel - Users mailing list archive at Nabble.com.
