[ 
https://issues.apache.org/jira/browse/CAMEL-26979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Federico Mariani reassigned CAMEL-26979:
----------------------------------------

    Assignee: Federico Mariani

> camel-quartz: quartz.properties at the classpath root or set by 
> -Dorg.quartz.properties is silently ignored
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-26979
>                 URL: https://issues.apache.org/jira/browse/CAMEL-26979
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-quartz
>    Affects Versions: 4.18.5, 4.22.2, 4.23.0
>            Reporter: Federico Mariani
>            Assignee: Federico Mariani
>            Priority: Minor
>             Fix For: 4.24.0
>
>
> When none of {{properties}}, {{propertiesRef}} or {{propertiesFile}} is set, 
> the quartz component loads only {{org/quartz/quartz.properties}}, the default 
> file inside quartz.jar. Quartz itself first reads the file named by 
> {{-Dorg.quartz.properties}}, then a {{quartz.properties}} at the classpath 
> root, so Camel ignores such a file without any log. The component docs 
> present this lookup as what Quartz does.
> Reproduction: put a {{quartz.properties}} with 
> {{org.quartz.threadPool.threadCount=3}} at the classpath root (or point 
> {{-Dorg.quartz.properties}} to a file) and start:
> {code:java}
> from("quartz://myGroup/myTimer?trigger.repeatInterval=1000").to("log:tick");
> {code}
> {{new StdSchedulerFactory().getScheduler()}} gets 3 threads, the Camel 
> scheduler gets 10 (the quartz.jar defaults).
> Expected: Camel logs a WARN that the file is not used and how to use it 
> ({{propertiesFile}}), and the docs say that Camel reads only 
> {{org/quartz/quartz.properties}} by default.
> _Claude Code on behalf of Federico Mariani_



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to