[AMQ-3024] Scheduler should support non-Kaha persistence

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.4.1
• Fix Version/s: 5.9.0
• Component/s: Broker
• Assignee: Unassigned
• Reporter: I D
• Created: 09/Nov/10 03:05
• Updated: 22/Jun/14 22:34
• Resolved: 26/Aug/13 19:06

Description

Currently, the persistence adapter attached to the broker service is simply ignored by the scheduler. The scheduler always uses KahaDB, instead.

I see two ways to go about this:

1. Creating a SchedulerPersistenceAdapter akin to (and possibly extending from) PersistenceAdapter, as well as a corresponding factory class and BrokerService property. This seems clumsy, but is in line with the approach currently taken, separating scheduler-related data from non-scheduler-related data - see BrokerService.setDataDirectoryFile() vs. BrokerService.setSchedulerDirectoryFile(). This approach is probably unnecessary, since the scheduler can clearly use existing PersistenceAdapters (or at least the KahaDB adapeter).
2. Depracating or removing the BrokerService.schedulerDirectoryFile property and having the scheduler use the one and only persistence adapter attached to the BrokerService (if it's a journaling adapter - BrokerService.dataDirectoryFile will be used, rather than BrokerService.schedulerDirectoryFile). This seems like the reasonable approach.

Issue Links

• is related to: AMQ-5238 Add JDBC Persistence for Scheduler
• is related to: AMQ-4068 Job Scheduler Store Growth is Unrestricted
• is superceded by: AMQ-4689 Allow for JobSchedulerStore implementations to be provided by the PersistenceAdapter