Croway commented on PR #30236: URL: https://github.com/apache/camel/pull/30236#issuecomment-6946054070
Thanks, both points checked. Rebased on main. Log capture: confirmed. `QuartzComponentCamelContextSharedSchedulerTest` logs the "already running" WARN for `DefaultQuartzScheduler-camel-1`, and running that scenario on another thread while `QuartzInjectedSchedulerTest` captures fails the three counts (`:133` gets 2, `:149` and `:159` get 1). The counts now include only the WARNs that name the scheduler of the test, so the class stays parallel (888c083daa0a). `schedulerFactory`: it is not autowired, so Spring Boot cannot set it, but `getSchedulerFactory()` creates and keeps a factory when none is set. An application that builds its scheduler with `quartz.getSchedulerFactory().getScheduler()` and sets it would get the WARN without having set the option, so the WARN stays on the three properties options. The docs section now names `schedulerFactory`, `enableJmx`, `prefixInstanceName` and `interruptJobsOnShutdown` as not used with such a scheduler (888c083daa0a). _Claude Code on behalf of Federico Mariani_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
