activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thomas Strauß (JIRA) <j...@apache.org>
Subject [jira] [Comment Edited] (AMQ-5238) Add JDBC Persistence for Scheduler
Date Fri, 07 Oct 2016 14:58:20 GMT

    [ https://issues.apache.org/jira/browse/AMQ-5238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15555302#comment-15555302
] 

Thomas Strauß edited comment on AMQ-5238 at 10/7/16 2:58 PM:
-------------------------------------------------------------

The situation got no better with the introduction of LevelDB, where you introduce a distributed
database with ZooKeeper and explicitely exclude the use of scheduled messages. 

If you research the topic, you may finally stumble on that, but you do this usually when you
fell into the trap of using redelivery policies in HA environments. 

It is nowhere clear from the documentation, that the scheduled messages and through the backdoor
of redelivery policies, also the messages prepared for redelivery are no longer covered by
the HA installation. This should be written explicitely on the redelivery policy documentation
page and on basically all pages describing HA setups.




was (Author: thst):
The situation got worse with the introduction of LevelDB, where you introduce a distributed
database with ZooKeeper and explicitely exclude the use of scheduled messages. 

If you research the topic, you may finally stumble on that, but you do this usually when you
fell into the trap of using redelivery policies in HA environments. 

It is nowhere clear from the documentation, that the scheduled messages and through the backdoor
of redelivery policies, also the messages prepared for redelivery are no longer covered by
the HA installation. This should be written explicitely on the redelivery policy documentation
page and on basically all pages describing HA setups.



> Add JDBC Persistence for Scheduler
> ----------------------------------
>
>                 Key: AMQ-5238
>                 URL: https://issues.apache.org/jira/browse/AMQ-5238
>             Project: ActiveMQ
>          Issue Type: New Feature
>          Components: Job Scheduler
>    Affects Versions: 5.9.0
>         Environment: JBoss A-MQ 6.0
>            Reporter: Jason Shepherd
>            Priority: Minor
>
> AMQ-3024 added support for non-KahaDB persistence of scheduled jobs, but a JDBC alternative
has yet to be added. 
> If we're using JDBC persistence adapter, we want all persistence for the broker to be
done for JDBC. Ideally this would also allows us to view historical statistics of the scheduler
as per AMQ-5192.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message