camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Seweryn Walendzik (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CAMEL-7371) Clustered Quartz trigger is paused by Camel on shutdown
Date Wed, 16 Apr 2014 07:39:14 GMT

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

Seweryn Walendzik updated CAMEL-7371:
-------------------------------------

    Description: 
Im using camel-quartz2 2.13.0 in Clustered mode, application is deployed on JBoss 7.1.1

On application shutdown the Quartz trigger state changed to PAUSED and after the next start
never changed to WAITING so never fired again.

Is it possible to configure quartz to resume trigger after the application restart?

In documentation 
{quote}
If you use Quartz in clustered mode, e.g. the JobStore is clustered. Then the Quartz2 component
will not pause/remove triggers when a node is being stopped/shutdown. This allows the trigger
to keep running on the other nodes in the cluster.
{quote}

quartz configuration 
{noformat}
org.quartz.scheduler.instanceName = ClusteredScheduler
org.quartz.scheduler.instanceId = AUTO
org.quartz.threadPool.class = org.quartz.simpl.SimpleThreadPool
org.quartz.threadPool.threadCount = 25
org.quartz.threadPool.threadPriority = 5

org.quartz.jobStore.misfireThreshold = 10000
org.quartz.jobStore.class = org.quartz.impl.jdbcjobstore.JobStoreTX
org.quartz.jobStore.driverDelegateClass = org.quartz.impl.jdbcjobstore.oracle.OracleDelegate
org.quartz.jobStore.useProperties = false
org.quartz.jobStore.dataSource = jobScheduler
org.quartz.jobStore.tablePrefix = QRTZ_

org.quartz.jobStore.isClustered = true
org.quartz.jobStore.clusterCheckinInterval = 20000

org.quartz.dataSource.jobScheduler.driver = oracle.jdbc.driver.OracleDriver
org.quartz.dataSource.jobScheduler.URL = jdbc:oracle:thin:@localhost:1521:xe
org.quartz.dataSource.jobScheduler.user = user
org.quartz.dataSource.jobScheduler.password = pass
org.quartz.dataSource.jobScheduler.maxConnections = 5
org.quartz.dataSource.jobScheduler.validationQuery=select 0 from dual
{noformat}



  was:
Im using camel-quartz2 2.13.0 in Clustered mode, application is deployed on JBoss 7.1.1

On application shutdown the Quartz trigger state changed to PAUSED and after the next start
never changed to WAITING so never fired again.

Is it possible to configure quartz to resume trigger after the application restart?

quartz configuration 
{noformat}
org.quartz.scheduler.instanceName = ClusteredScheduler
org.quartz.scheduler.instanceId = AUTO
org.quartz.threadPool.class = org.quartz.simpl.SimpleThreadPool
org.quartz.threadPool.threadCount = 25
org.quartz.threadPool.threadPriority = 5

org.quartz.jobStore.misfireThreshold = 10000
org.quartz.jobStore.class = org.quartz.impl.jdbcjobstore.JobStoreTX
org.quartz.jobStore.driverDelegateClass = org.quartz.impl.jdbcjobstore.oracle.OracleDelegate
org.quartz.jobStore.useProperties = false
org.quartz.jobStore.dataSource = jobScheduler
org.quartz.jobStore.tablePrefix = QRTZ_

org.quartz.jobStore.isClustered = true
org.quartz.jobStore.clusterCheckinInterval = 20000

org.quartz.dataSource.jobScheduler.driver = oracle.jdbc.driver.OracleDriver
org.quartz.dataSource.jobScheduler.URL = jdbc:oracle:thin:@localhost:1521:xe
org.quartz.dataSource.jobScheduler.user = user
org.quartz.dataSource.jobScheduler.password = pass
org.quartz.dataSource.jobScheduler.maxConnections = 5
org.quartz.dataSource.jobScheduler.validationQuery=select 0 from dual
{noformat}




> Clustered Quartz trigger is paused by Camel on shutdown
> -------------------------------------------------------
>
>                 Key: CAMEL-7371
>                 URL: https://issues.apache.org/jira/browse/CAMEL-7371
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-quartz2
>    Affects Versions: 2.13.0
>            Reporter: Seweryn Walendzik
>
> Im using camel-quartz2 2.13.0 in Clustered mode, application is deployed on JBoss 7.1.1
> On application shutdown the Quartz trigger state changed to PAUSED and after the next
start never changed to WAITING so never fired again.
> Is it possible to configure quartz to resume trigger after the application restart?
> In documentation 
> {quote}
> If you use Quartz in clustered mode, e.g. the JobStore is clustered. Then the Quartz2
component will not pause/remove triggers when a node is being stopped/shutdown. This allows
the trigger to keep running on the other nodes in the cluster.
> {quote}
> quartz configuration 
> {noformat}
> org.quartz.scheduler.instanceName = ClusteredScheduler
> org.quartz.scheduler.instanceId = AUTO
> org.quartz.threadPool.class = org.quartz.simpl.SimpleThreadPool
> org.quartz.threadPool.threadCount = 25
> org.quartz.threadPool.threadPriority = 5
> org.quartz.jobStore.misfireThreshold = 10000
> org.quartz.jobStore.class = org.quartz.impl.jdbcjobstore.JobStoreTX
> org.quartz.jobStore.driverDelegateClass = org.quartz.impl.jdbcjobstore.oracle.OracleDelegate
> org.quartz.jobStore.useProperties = false
> org.quartz.jobStore.dataSource = jobScheduler
> org.quartz.jobStore.tablePrefix = QRTZ_
> org.quartz.jobStore.isClustered = true
> org.quartz.jobStore.clusterCheckinInterval = 20000
> org.quartz.dataSource.jobScheduler.driver = oracle.jdbc.driver.OracleDriver
> org.quartz.dataSource.jobScheduler.URL = jdbc:oracle:thin:@localhost:1521:xe
> org.quartz.dataSource.jobScheduler.user = user
> org.quartz.dataSource.jobScheduler.password = pass
> org.quartz.dataSource.jobScheduler.maxConnections = 5
> org.quartz.dataSource.jobScheduler.validationQuery=select 0 from dual
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message