I'm running an endpoint of: quartz2://job/deviceDetailsUsageTimer48?cron=0+0+04+*+*+?&trigger.timeZone=GMT&trigger.misfireInstruction=2
on an amazon ec2 instance that has the timezone set to UTC. My expectation is that the job should go off at 4am GMT based on the quartz2 endpoint configuration, but the logs on the ec2 instance show it triggered at 2017-02-01 03:00:07. A one hour difference. Does anyone know why this might be the case? -- View this message in context: http://camel.465427.n5.nabble.com/quartz2-endpoint-timezone-issue-tp5793333.html Sent from the Camel - Users mailing list archive at Nabble.com.
