On Mon, Jan 28, 2013 at 12:46 AM, garrydias <garryd...@gmail.com> wrote: > 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. >
Ah well in fact we fixed an issue in the upcoming Camel releases related to this, hitting the cache limit. This should be fixed in next releases of Camel. > 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. -- Claus Ibsen ----------------- Red Hat, Inc. FuseSource is now part of Red Hat Email: cib...@redhat.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
