[
https://issues.apache.org/jira/browse/ARTEMIS-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16330554#comment-16330554
]
ASF GitHub Bot commented on ARTEMIS-1587:
-----------------------------------------
Github user mtaylor commented on the issue:
https://github.com/apache/activemq-artemis/pull/1775
Sorry guys but I am -1 on this. I thought the idea of this was to behave
in a similar way to default-max-consumers, or default-purge-on-no-consumers. I
am not happy about overriding the protocol handlers behaviour in this way. I
can see value in a default-queue-durability setting, for cases when it's not
known. Can the original requirement not be addressed using auto-delete-queues
and non-durable messages? If non-durable queues/temps are really required, how
about a persistence=false address-setting instead?
> Add setting to control the queue durable property for auto-created addresses
> ----------------------------------------------------------------------------
>
> Key: ARTEMIS-1587
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1587
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Components: Broker
> Affects Versions: 2.4.0
> Reporter: Johan Stenberg
> Assignee: Martyn Taylor
> Priority: Major
>
> When pre-defining queues in the broker.xml the durable property can be
> specified. Auto-created queues are currently always durable. It would be
> useful to extend the AddressSettings so that default queue durability for
> auto-created queues can be specified.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
