Hi, > But I somehow it is failing and I am not able to get complete stacktrace > of > exception.
"To fail somehow" is a bit vague term :) . Could you elaborate what exactly is wrong with your message processing? -- That is the problem, I am running Camel route and when i tried to retrieve Exception Stack Trace in onException route, i am not getting any exception stack trace; just camel exception as I mentioned in my initial post. > org.apache.camel.component.velocity.VelocityEndpoint ¬ Runtime : ran out > of > parsers. Creating a new one. Please increment the parser.pool.size > property. This only slows down message processing since Velocity needs to create additional parsers. But the processing should work correctly. -- I think you are right it is just an INFO message in logs, but I was just wondering if this problem cause camel to fail route and stop further processing. Can you provider us more information? What exactly gets wrong? Ideally you could try to reproduce the problem with minimal Maven project with test case attached - then we will help you to fix the problem for 100% :) . -- I am just trying to use velocity to generate email body, but my route keep failing and I am not getting any stack trace so can not pin point the actual exception/cause. I will try to give you a small test case with my route. -- View this message in context: http://camel.465427.n5.nabble.com/Camel-Velocity-Template-throwing-error-tp5715388p5715412.html Sent from the Camel - Users mailing list archive at Nabble.com.
