[CAMEL-10606] Modify quartz2 endpoint to be a singleton

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.17.5, 2.18.2, 2.19.0
• Component/s: camel-quartz2
• Estimated Complexity: Unknown
• Assignee: James Netherton
• Reporter: James Netherton
• Created: 15/Dec/16 15:42
• Updated: 15/Dec/16 16:56
• Resolved: 15/Dec/16 16:49

Description

Currently the quartz2 endpoint implements isSingleton() and returns false.

This causes issues if you try to do something like:

camelContext.getEndpoint("quartz2://foo?cron=5+*+*+*+*")

Which can trigger the endpoint start() method to be called and results in:

Caused by: java.lang.IllegalArgumentException: Trigger key myGroup.longPeriodTimer is already in use by quartz2://foo/longPeriodTimer?cron=5+*+*+*+*
	at org.apache.camel.component.quartz2.QuartzEndpoint.ensureNoDupTriggerKey(QuartzEndpoint.java:446)
	at org.apache.camel.component.quartz2.QuartzEndpoint.addJobInScheduler(QuartzEndpoint.java:380)
	at org.apache.camel.component.quartz2.QuartzEndpoint.doStart(QuartzEndpoint.java:340)

The quartz1 endpoint implements isSingleton to return true. I see no reason why quartz2 should be any different.

Issue Links

• links to: GitHub Pull Request #1350