activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Pavlovich (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARTEMIS-869) Extend DeliveryMode to add a "LAZY_PERSISTENCE" option
Date Mon, 05 Dec 2016 18:42:58 GMT

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

Matt Pavlovich commented on ARTEMIS-869:
----------------------------------------

[~tabish121] Yeah, I think its one of those corner cases where the JMS API is specific on
what is allowed for delivery mode, but doesn't go as far as being that specific with things
other "int" values (like ACK modes). 

Its definitely an extension / break from JMS API, but I feel it is safe (users will have to
use a specified class out of o.a.activemq...) and there is precedence for doing similar with
ack modes in ActiveMQ 5.x and DeliveryMode in Tibco EMS. 

> Extend DeliveryMode to add a "LAZY_PERSISTENCE" option
> ------------------------------------------------------
>
>                 Key: ARTEMIS-869
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-869
>             Project: ActiveMQ Artemis
>          Issue Type: New Feature
>          Components: Broker
>            Reporter: Matt Pavlovich
>
> Currently the JMS Spec defines two delivery modes-- NON_PERSISTENT and PERSISTENT. Similar
to how the ACK modes have been extended, it would be handy to extend the DeliveryMode to support
a Kafka-like use case where the message should be persisted, but not require a sync() before
being ack'd. 
> Currently, the only way to define this in ActiveMQ 5.x is the periodic option on KahaDB,
which effects all messages. It would be handy to be able to also define it at the per-message
level
> Ideas on option:
> ActiveMQDeliveryMode.LAZY_PERSISTENCE



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

Mime
View raw message