Thanx Christian. You are right. Set Exchange.MAXIMUM_ENDPOINT_CACHE_SIZE property before camel1.start() is the key to solve my problem.
This is not a bug after all. Thanx again []s -- View this message in context: http://camel.465427.n5.nabble.com/Camel-Quartz-Bug-tp5726285p5726392.html Sent from the Camel - Users mailing list archive at Nabble.com.
