camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CAMEL-3336) Quartz component has minor issues with old versions of Quartz
Date Fri, 12 Nov 2010 10:09:25 GMT

    [ https://issues.apache.org/activemq/browse/CAMEL-3336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63295#action_63295
] 

Claus Ibsen commented on CAMEL-3336:
------------------------------------

There is no guarantee that we support older versions of quartz. The component is build with
1.8.x.

> Quartz component has minor issues with old versions of Quartz
> -------------------------------------------------------------
>
>                 Key: CAMEL-3336
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3336
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-quartz
>    Affects Versions: 2.5.0
>            Reporter: Savas Ali Tokmen
>            Priority: Minor
>             Fix For: 2.6.0
>
>         Attachments: camel-quartz-1.6-1.7-support.patch
>
>
> Hello
> I have run into two issues using camel-quartz with old versions of Quartz (Quartz 1.6
and 1.7):
> 1. With Quartz 1.6, at shutdown, I get a message:
> {noformat}
> 2010-11-12 02:41:22,965 DefaultShutdownStrategy.shutdownNow Error occurred while shutting
down route: Consumer[quartz://importAnnuaireAgentsTimer?cron=0+30+2+*+*+%3F]. This exception
will be ignored.
> java.lang.NoSuchMethodError: org.quartz.SchedulerMetaData.isJobStoreClustered()Z
> 	at org.apache.camel.component.quartz.QuartzComponent.isClustered(QuartzComponent.java:278)
> 	at org.apache.camel.component.quartz.QuartzComponent.removeJob(QuartzComponent.java:238)
> 	at org.apache.camel.component.quartz.QuartzEndpoint.removeTrigger(QuartzEndpoint.java:84)
> 	at org.apache.camel.component.quartz.QuartzEndpoint.consumerStopped(QuartzEndpoint.java:221)
> 	at org.apache.camel.component.quartz.QuartzConsumer.doStop(QuartzConsumer.java:44)
> 	at org.apache.camel.impl.ServiceSupport.stop(ServiceSupport.java:98)
> 	at org.apache.camel.impl.ServiceSupport.stop(ServiceSupport.java:122)
> 	at org.apache.camel.util.ServiceHelper.stopService(ServiceHelper.java:99)
> 	at org.apache.camel.impl.DefaultShutdownStrategy.shutdownNow(DefaultShutdownStrategy.java:235)
> 	at org.apache.camel.impl.DefaultShutdownStrategy$ShutdownTask.run(DefaultShutdownStrategy.java:386)
> 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> 	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> 	at java.lang.Thread.run(Thread.java:619)
> {noformat}
> 2. Starting of a delayed timer fails. I think warning the user would be a better idea.
> Patch is attached (it basically catches the NoSuchMethodError exceptions and acts accordingly)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message