[
https://issues.apache.org/jira/browse/AMQ-3024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-3024.
-------------------------------
Resolution: Fixed
Fix Version/s: (was: NEEDS_REVIEWED)
5.9.0
This is fixed by AMQ-4689 which allows for the persistence adapter to implement
JobSchedulerStore or for a custom scheduler to be configured via the
setJobSchedulerStore method on broker service. For now the set method for
scheduler dir remains for backwards compat as the KahaDB variant is the only
one in existence right now.
> Scheduler should support non-Kaha persistence
> ---------------------------------------------
>
> Key: AMQ-3024
> URL: https://issues.apache.org/jira/browse/AMQ-3024
> Project: ActiveMQ
> Issue Type: New Feature
> Components: Broker
> Affects Versions: 5.4.1
> Reporter: I D
> Fix For: 5.9.0
>
>
> 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:
> # 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).
> # 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
