[ https://issues.apache.org/jira/browse/CAMEL-7754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14117108#comment-14117108 ]
Charles Moulliard commented on CAMEL-7754: ------------------------------------------ There is a bug with Quartz Scheduler as the TIMEZONE which is well used by the calendar is not taken into consideration when the nextFiredTime is calculated by the CronExpression class {code} protected Date getTimeAfter(Date afterTime) { // Computation is based on Gregorian year only. Calendar cl = new java.util.GregorianCalendar(getTimeZone()); // move ahead one second, since we're computing the time *after* the // given time afterTime = new Date(afterTime.getTime() + 1000); // CALENDAR SYSTEM IS USED {code} See screenshots > Property Trigger.timerZone is declared as constant but not implemented > ---------------------------------------------------------------------- > > Key: CAMEL-7754 > URL: https://issues.apache.org/jira/browse/CAMEL-7754 > Project: Camel > Issue Type: Bug > Components: camel-quartz, camel-quartz2 > Affects Versions: 2.12.1, 2.13.2 > Reporter: Charles Moulliard > Assignee: Charles Moulliard > Fix For: 2.14.0 > > > Seems that we have a problem with Quartz/Quartz2 components. The doc claims > that we can setup this property in the URI "trigger.timeZone" > (http://camel.apache.org/quartz.html - see specifying timezone ) but quartz > don't use it even if a constant is defined > :https://www.dropbox.com/s/1wjt3slsz3jajlh/Screenshot%202014-08-27%2010.29.53.png?dl=0 > We have the same issue too with quartz2 --> > https://www.dropbox.com/s/jcxnn72bzi38qob/Screenshot%202014-08-27%2010.31.34.png?dl=0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)