activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Mikheev (JIRA)" <>
Subject [jira] [Commented] (AMQ-3024) Scheduler should support non-Kaha persistence
Date Tue, 04 Mar 2014 23:07:43 GMT


Oleg Mikheev commented on AMQ-3024:

JobSchedulerStore assumes that it is directory based.
By non-Kaha persistence I would assume non file-based persistence.
Is there a separate issue for that?

> Scheduler should support non-Kaha persistence
> ---------------------------------------------
>                 Key: AMQ-3024
>                 URL:
>             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 was sent by Atlassian JIRA

View raw message