[jira] [Commented] (CAMEL-7454) Camel-Quartz2 Scheduler Name Difference
[
https://issues.apache.org/jira/browse/CAMEL-7454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16908241#comment-16908241
]
Balu Sasidharan Pillai commented on CAMEL-7454:
---
Thanks [~Luckless] for posting this issue. My search for answer landed in this
issue you created years ago.
> Camel-Quartz2 Scheduler Name Difference
> ---
>
> Key: CAMEL-7454
> URL: https://issues.apache.org/jira/browse/CAMEL-7454
> Project: Camel
> Issue Type: Improvement
> Components: camel-quartz2
>Affects Versions: 2.13.0
>Reporter: Dakota Brown
>Assignee: Claus Ibsen
>Priority: Minor
> Labels: quartz
> Fix For: 2.16.0
>
>
> We have a situation where we have multiple quartz routes in different camel
> contexts. We want to have the same scheduler name for these schedulers.
> In camel-quartz2 version 2.12.2, it works as expected.
> In camel-quartz2 version 2.13.0, each scheduler is appended with the
> context's name.
> *Files*
> {code:title = quartz.LOCAL.properties|borderStyle=solid}
> #
> # Configure Main Scheduler Properties
> #
> org.quartz.scheduler.instanceName = Test2
> org.quartz.scheduler.instanceId = AUTO
> #
> # Configure ThreadPool
> #
> org.quartz.threadPool.class = org.quartz.simpl.SimpleThreadPool
> org.quartz.threadPool.threadCount = 25
> org.quartz.threadPool.threadPriority = 5
> #
> # Configure JobStore
> #
> org.quartz.jobStore.class = org.quartz.impl.jdbcjobstore.JobStoreTX
> org.quartz.jobStore.driverDelegateClass =
> org.quartz.impl.jdbcjobstore.oracle.OracleDelegate
> org.quartz.jobStore.useProperties = true
> org.quartz.jobStore.dataSource = myDS
> org.quartz.jobStore.tablePrefix = QRTZ_
> org.quartz.jobStore.isClustered = true
> org.quartz.jobStore.clusterCheckinInterval = 2
> org.quartz.dataSource.myDS.driver = oracle.jdbc.driver.OracleDriver
> org.quartz.dataSource.myDS.URL = jdbc:oracle:thin:@XXX
> org.quartz.dataSource.myDS.user = X
> org.quartz.dataSource.myDS.password =
> org.quartz.dataSource.myDS.maxConnections = 5
> org.quartz.dataSource.myDS.validationQuery=select 0 from dual
> #
> # Configure Trigger Logging
> #
> org.quartz.plugin.triggHistory.class =
> org.quartz.plugins.history.LoggingTriggerHistoryPlugin
> org.quartz.plugin.triggHistory.triggerFiredMessage = Trigger \{1\}.\{0\}
> fired job \{6\}.\{5\} at: \{4, date, HH:mm:ss MM/dd/}
> org.quartz.plugin.triggHistory.triggerCompleteMessage = Trigger \{1\}.\{0\}
> completed firing job \{6\}.\{5\} at \{4, date, HH:mm:ss MM/dd/\}.
> {code}
> {code:title = TestContext1.xml|borderStyle=solid}
>
> http://www.springframework.org/schema/beans;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xmlns:camel="http://camel.apache.org/schema/spring;
> xmlns:context="http://www.springframework.org/schema/context;
> xmlns:util="http://www.springframework.org/schema/util;
> xsi:schemaLocation="
>http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans.xsd
>http://www.springframework.org/schema/context
> http://www.springframework.org/schema/context/spring-context-3.0.xsd
>http://camel.apache.org/schema/spring
> http://camel.apache.org/schema/spring/camel-spring.xsd
>http://www.springframework.org/schema/util
> http://www.springframework.org/schema/util/spring-util.xsd;>
> class="org.apache.camel.component.quartz2.QuartzComponent">
>value="config/quartz/quartz.LOCAL.properties" />
>
>xmlns="http://camel.apache.org/schema/spring;
> xmlns:oas="http://www.verizonwireless.com/oas;>
>
>uri="quartz1://RSSX/test1?pauseJob=falsedeleteJob=falsestateful=truecron=30+*+*+*+*+?"
> />
>
>
>
>
>
>
>
> {code}
> *Results*
> Running camel-quartz2 version 2.12.2:
> {code:xml}
> Quartz scheduler 'Test2' initialized from an externally provided properties
> instance.
> {code}
> Running camel-quartz2 version 2.13.0:
> {code:xml}
> Quartz scheduler 'Test2-TestContext1' initialized from an externally provided
>
[jira] [Commented] (CAMEL-7454) Camel-Quartz2 Scheduler Name Difference
[
https://issues.apache.org/jira/browse/CAMEL-7454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14228683#comment-14228683
]
Claus Ibsen commented on CAMEL-7454:
We could likely add some option where you can turn this on|off.
Camel-Quartz2 Scheduler Name Difference
---
Key: CAMEL-7454
URL: https://issues.apache.org/jira/browse/CAMEL-7454
Project: Camel
Issue Type: Improvement
Components: camel-quartz2
Affects Versions: 2.13.0
Reporter: Dakota Brown
Assignee: Claus Ibsen
Priority: Minor
Labels: quartz
Fix For: 2.15.0
We have a situation where we have multiple quartz routes in different camel
contexts. We want to have the same scheduler name for these schedulers.
In camel-quartz2 version 2.12.2, it works as expected.
In camel-quartz2 version 2.13.0, each scheduler is appended with the
context's name.
*Files*
{code:title = quartz.LOCAL.properties|borderStyle=solid}
#
# Configure Main Scheduler Properties
#
org.quartz.scheduler.instanceName = Test2
org.quartz.scheduler.instanceId = AUTO
#
# Configure ThreadPool
#
org.quartz.threadPool.class = org.quartz.simpl.SimpleThreadPool
org.quartz.threadPool.threadCount = 25
org.quartz.threadPool.threadPriority = 5
#
# Configure JobStore
#
org.quartz.jobStore.class = org.quartz.impl.jdbcjobstore.JobStoreTX
org.quartz.jobStore.driverDelegateClass =
org.quartz.impl.jdbcjobstore.oracle.OracleDelegate
org.quartz.jobStore.useProperties = true
org.quartz.jobStore.dataSource = myDS
org.quartz.jobStore.tablePrefix = QRTZ_
org.quartz.jobStore.isClustered = true
org.quartz.jobStore.clusterCheckinInterval = 2
org.quartz.dataSource.myDS.driver = oracle.jdbc.driver.OracleDriver
org.quartz.dataSource.myDS.URL = jdbc:oracle:thin:@XXX
org.quartz.dataSource.myDS.user = X
org.quartz.dataSource.myDS.password =
org.quartz.dataSource.myDS.maxConnections = 5
org.quartz.dataSource.myDS.validationQuery=select 0 from dual
#
# Configure Trigger Logging
#
org.quartz.plugin.triggHistory.class =
org.quartz.plugins.history.LoggingTriggerHistoryPlugin
org.quartz.plugin.triggHistory.triggerFiredMessage = Trigger \{1\}.\{0\}
fired job \{6\}.\{5\} at: \{4, date, HH:mm:ss MM/dd/}
org.quartz.plugin.triggHistory.triggerCompleteMessage = Trigger \{1\}.\{0\}
completed firing job \{6\}.\{5\} at \{4, date, HH:mm:ss MM/dd/\}.
{code}
{code:title = TestContext1.xml|borderStyle=solid}
?xml version=1.0 encoding=UTF-8?
beans xmlns=http://www.springframework.org/schema/beans;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xmlns:camel=http://camel.apache.org/schema/spring;
xmlns:context=http://www.springframework.org/schema/context;
xmlns:util=http://www.springframework.org/schema/util;
xsi:schemaLocation=
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd
http://www.springframework.org/schema/context
http://www.springframework.org/schema/context/spring-context-3.0.xsd
http://camel.apache.org/schema/spring
http://camel.apache.org/schema/spring/camel-spring.xsd
http://www.springframework.org/schema/util
http://www.springframework.org/schema/util/spring-util.xsd;
bean id=quartz1
class=org.apache.camel.component.quartz2.QuartzComponent
property name=propertiesFile
value=config/quartz/quartz.LOCAL.properties /
/bean
camelContext id=TestContext1
xmlns=http://camel.apache.org/schema/spring;
xmlns:oas=http://www.verizonwireless.com/oas;
route id=route1
from
uri=quartz1://RSSX/test1?pauseJob=falseamp;deleteJob=falseamp;stateful=trueamp;cron=30+*+*+*+*+?
/
log message=${header.scheduler} fired route 1/
/route
/camelContext
/beans
{code}
*Results*
Running camel-quartz2 version 2.12.2:
{code:xml}
Quartz scheduler 'Test2' initialized from an externally provided properties
instance.
{code}
Running camel-quartz2 version 2.13.0:
{code:xml}
Quartz scheduler
[jira] [Commented] (CAMEL-7454) Camel-Quartz2 Scheduler Name Difference
[
https://issues.apache.org/jira/browse/CAMEL-7454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14006844#comment-14006844
]
Claus Ibsen commented on CAMEL-7454:
This is intended as the scheduler name should be unique.
Why do you want different schedulers to have the same name?
Camel-Quartz2 Scheduler Name Difference
---
Key: CAMEL-7454
URL: https://issues.apache.org/jira/browse/CAMEL-7454
Project: Camel
Issue Type: Improvement
Components: camel-quartz2
Affects Versions: 2.13.0
Reporter: Dakota Brown
Priority: Minor
Labels: quartz
We have a situation where we have multiple quartz routes in different camel
contexts. We want to have the same scheduler name for these schedulers.
In camel-quartz2 version 2.12.2, it works as expected.
In camel-quartz2 version 2.13.0, each scheduler is appended with the
context's name.
*Files*
{code:title = quartz.LOCAL.properties|borderStyle=solid}
#
# Configure Main Scheduler Properties
#
org.quartz.scheduler.instanceName = Test2
org.quartz.scheduler.instanceId = AUTO
#
# Configure ThreadPool
#
org.quartz.threadPool.class = org.quartz.simpl.SimpleThreadPool
org.quartz.threadPool.threadCount = 25
org.quartz.threadPool.threadPriority = 5
#
# Configure JobStore
#
org.quartz.jobStore.class = org.quartz.impl.jdbcjobstore.JobStoreTX
org.quartz.jobStore.driverDelegateClass =
org.quartz.impl.jdbcjobstore.oracle.OracleDelegate
org.quartz.jobStore.useProperties = true
org.quartz.jobStore.dataSource = myDS
org.quartz.jobStore.tablePrefix = QRTZ_
org.quartz.jobStore.isClustered = true
org.quartz.jobStore.clusterCheckinInterval = 2
org.quartz.dataSource.myDS.driver = oracle.jdbc.driver.OracleDriver
org.quartz.dataSource.myDS.URL = jdbc:oracle:thin:@XXX
org.quartz.dataSource.myDS.user = X
org.quartz.dataSource.myDS.password =
org.quartz.dataSource.myDS.maxConnections = 5
org.quartz.dataSource.myDS.validationQuery=select 0 from dual
#
# Configure Trigger Logging
#
org.quartz.plugin.triggHistory.class =
org.quartz.plugins.history.LoggingTriggerHistoryPlugin
org.quartz.plugin.triggHistory.triggerFiredMessage = Trigger \{1\}.\{0\}
fired job \{6\}.\{5\} at: \{4, date, HH:mm:ss MM/dd/}
org.quartz.plugin.triggHistory.triggerCompleteMessage = Trigger \{1\}.\{0\}
completed firing job \{6\}.\{5\} at \{4, date, HH:mm:ss MM/dd/\}.
{code}
{code:title = TestContext1.xml|borderStyle=solid}
?xml version=1.0 encoding=UTF-8?
beans xmlns=http://www.springframework.org/schema/beans;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xmlns:camel=http://camel.apache.org/schema/spring;
xmlns:context=http://www.springframework.org/schema/context;
xmlns:util=http://www.springframework.org/schema/util;
xsi:schemaLocation=
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd
http://www.springframework.org/schema/context
http://www.springframework.org/schema/context/spring-context-3.0.xsd
http://camel.apache.org/schema/spring
http://camel.apache.org/schema/spring/camel-spring.xsd
http://www.springframework.org/schema/util
http://www.springframework.org/schema/util/spring-util.xsd;
bean id=quartz1
class=org.apache.camel.component.quartz2.QuartzComponent
property name=propertiesFile
value=config/quartz/quartz.LOCAL.properties /
/bean
camelContext id=TestContext1
xmlns=http://camel.apache.org/schema/spring;
xmlns:oas=http://www.verizonwireless.com/oas;
route id=route1
from
uri=quartz1://RSSX/test1?pauseJob=falseamp;deleteJob=falseamp;stateful=trueamp;cron=30+*+*+*+*+?
/
log message=${header.scheduler} fired route 1/
/route
/camelContext
/beans
{code}
*Results*
Running camel-quartz2 version 2.12.2:
{code:xml}
Quartz scheduler 'Test2' initialized from an externally provided properties
instance.
{code}
Running camel-quartz2 version 2.13.0:
{code:xml}
Quartz scheduler 'Test2-TestContext1'
[jira] [Commented] (CAMEL-7454) Camel-Quartz2 Scheduler Name Difference
[
https://issues.apache.org/jira/browse/CAMEL-7454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007105#comment-14007105
]
Dakota Brown commented on CAMEL-7454:
-
We have a front end application to enable and disable these quartz jobs by
Autowiring the scheduler defined below:
{code:xml}
beans:bean id=schedulerFactoryBean
class=org.springframework.scheduling.quartz.SchedulerFactoryBean
beans:property name=applicationContextSchedulerContextKey
beans:valueapplicationContext/beans:value
/beans:property
beans:property name=schedulerName value=Test2/
beans:property name=autoStartup value=false/
beans:property name=quartzProperties
beans:props
beans:prop
key=org.quartz.scheduler.instanceNameTest2/beans:prop
beans:prop
key=org.quartz.scheduler.instanceId14/beans:prop
beans:prop
key=org.quartz.jobStore.classorg.quartz.impl.jdbcjobstore.JobStoreTX/beans:prop
beans:prop
key=org.quartz.scheduler.skipUpdateChecktrue/beans:prop
beans:prop
key=org.quartz.jobStore.driverDelegateClassorg.quartz.impl.jdbcjobstore.oracle.OracleDelegate/beans:prop
beans:prop
key=org.quartz.jobStore.usePropertiestrue/beans:prop
beans:prop
key=org.quartz.jobStore.dataSourcemyDS/beans:prop
beans:prop
key=org.quartz.jobStore.isClusteredtrue/beans:prop
beans:prop
key=org.quartz.jobStore.clusterCheckinInterval2/beans:prop
beans:prop
key=org.quartz.dataSource.myDS.driveroracle.jdbc.driver.OracleDriver/beans:prop
beans:prop
key=org.quartz.dataSource.myDS.URLjdbc:oracle:thin:@XX/beans:prop
beans:prop
key=org.quartz.dataSource.myDS.userXXX/beans:prop
beans:prop
key=org.quartz.dataSource.myDS.passwordXXX/beans:prop
beans:prop
key=org.quartz.dataSource.myDS.maxConnections1/beans:prop
beans:prop
key=org.quartz.dataSource.myDS.validationQueryselect 0 from dual/beans:prop
/beans:props
/beans:property
/beans:bean
{code}
It's nice having one scheduler to reference instead of multiple schedulers
dependent on the camel context names (and contexts to be added in the future).
While the jobs are in different contexts, we wanted one scheduler to control
all of them. This change in 2.13.0 effectively broke our quartz job manager.
Camel-Quartz2 Scheduler Name Difference
---
Key: CAMEL-7454
URL: https://issues.apache.org/jira/browse/CAMEL-7454
Project: Camel
Issue Type: Improvement
Components: camel-quartz2
Affects Versions: 2.13.0
Reporter: Dakota Brown
Assignee: Claus Ibsen
Priority: Minor
Labels: quartz
We have a situation where we have multiple quartz routes in different camel
contexts. We want to have the same scheduler name for these schedulers.
In camel-quartz2 version 2.12.2, it works as expected.
In camel-quartz2 version 2.13.0, each scheduler is appended with the
context's name.
*Files*
{code:title = quartz.LOCAL.properties|borderStyle=solid}
#
# Configure Main Scheduler Properties
#
org.quartz.scheduler.instanceName = Test2
org.quartz.scheduler.instanceId = AUTO
#
# Configure ThreadPool
#
org.quartz.threadPool.class = org.quartz.simpl.SimpleThreadPool
org.quartz.threadPool.threadCount = 25
org.quartz.threadPool.threadPriority = 5
#
# Configure JobStore
#
org.quartz.jobStore.class = org.quartz.impl.jdbcjobstore.JobStoreTX
org.quartz.jobStore.driverDelegateClass =
org.quartz.impl.jdbcjobstore.oracle.OracleDelegate
org.quartz.jobStore.useProperties = true
org.quartz.jobStore.dataSource = myDS
org.quartz.jobStore.tablePrefix = QRTZ_
org.quartz.jobStore.isClustered = true
org.quartz.jobStore.clusterCheckinInterval = 2
org.quartz.dataSource.myDS.driver = oracle.jdbc.driver.OracleDriver
org.quartz.dataSource.myDS.URL =
