Thanks Claus. I redesigned my scheduler project to solve my problem but is a matter of time until my application start more than 1000 again.
I couldn´t find nothing related to "reasonable" stateful job limit in the Quartz docs. Using plain quartz this problem does not happens. Using plain Quartz I could also fire over 5000 jobs facing a slow down at the job execution(expected behavior of StatefulJob) only. And change the threadCount to a different than 10 (default defined by camel-quarz), the problem still reamains. Camel logs the output bellow, indicating that 100 threads are started but it is unable to fire more than 1000 jobs. /279 [main] INFO org.apache.camel.impl.DefaultCamelContext - Apache Camel 2.9.2 (CamelContext: camel-1) is starting 280 [main] INFO org.apache.camel.management.ManagementStrategyFactory - JMX enabled. Using ManagedManagementStrategy. 416 [main] INFO org.apache.camel.management.DefaultManagementLifecycleStrategy - StatisticsLevel at All so enabling load performance statistics 502 [main] INFO org.apache.camel.impl.converter.AnnotationTypeConverterLoader - Found 3 packages with 15 @Converter classes to load 522 [main] INFO org.apache.camel.impl.converter.DefaultTypeConverter - Loaded 170 core type converters (total 170 type converters) 526 [main] INFO org.apache.camel.impl.converter.AnnotationTypeConverterLoader - Loaded 2 @Converter classes 532 [main] INFO org.apache.camel.impl.converter.DefaultTypeConverter - Loaded additional 9 type converters (total 179 type converters) in 0.009 seconds 544 [main] INFO org.apache.camel.component.quartz.QuartzComponent - Loading Quartz properties file from classpath: quartz.properties 592 [main] INFO org.quartz.core.SchedulerSignalerImpl - Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl 592 [main] INFO org.quartz.core.QuartzScheduler - Quartz Scheduler v.1.8.5 created. 594 [main] INFO org.quartz.simpl.RAMJobStore - RAMJobStore initialized. 594 [main] INFO org.quartz.core.QuartzScheduler - Scheduler meta-data: Quartz Scheduler (v1.8.5) 'QuartzScheduler' with instanceId 'NON_CLUSTERED' Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally. NOT STARTED. Currently in standby mode. Number of jobs executed: 0 Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 100 threads. Using job-store 'org.quartz.simpl.RAMJobStore' - which does not support persistence. and is not clustered. 594 [main] INFO org.quartz.impl.StdSchedulerFactory - Quartz scheduler 'QuartzScheduler' initialized from an externally provided properties instance. 594 [main] INFO org.quartz.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.com/Camel-Quartz-Bug-tp5726285p5726336.html Sent from the Camel - Users mailing list archive at Nabble.com.
