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
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
ggered Jobs: 1200
> Fired Jobs: 200
> camel-quartz-test.txt
> <http://camel.465427.n5.nabble.com/file/n5726337/camel-quartz-test.txt>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Camel-Quartz-Bug-tp5726285p5726337.html
> Sent from
artz.impl.StdSchedulerFactory - Quartz scheduler
version: 1.8.5/
The worse case of this fail I see starting 1200 jobs: camel-quartz always
fire only 200 of these jobs. Doesn´t matter the thread pool size .
Thanks again.
Nice weekend
--
View this message in context:
http://camel.465427.n5.nabble.c
routes that trigger almost
> the same quartz cron trigger?
>
Oh and you may want to add more threads to the quartz scheduler so it
has more power
as you trigger the jobs at the same time.
You can configure this in the quartz.properties file for example.
>
>> Thanx
>>
&g
xt:
> http://camel.465427.n5.nabble.com/Camel-Quartz-Bug-tp5726285p5726288.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: dav
.465427.n5.nabble.com/file/n5726285/pom.xml>
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-Quartz-Bug-tp5726285.html
Sent from the Camel - Users mailing list archive at Nabble.com.
