You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Justin Bertram (JIRA)" <ji...@apache.org> on 2016/12/03 01:14:58 UTC

[jira] [Commented] (ARTEMIS-869) Extend DeliveryMode to add a "LAZY_PERSISTENCE" option

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

Justin Bertram commented on ARTEMIS-869:
----------------------------------------

This is already available via the {{blockOnDurableSend}} configuration parameter on the core {{ServerLocator}} (which can be set on the URL used when creating the JMS connection factory).  It may not be as flexible as a JMS DeliveryMode extension because it is tied to the JMS connection rather than the JMS producer, but my guess is it would be sufficient for most (all?) use-cases that need such functionality.

> 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)