You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2019/05/07 15:30:00 UTC
[jira] [Resolved] (QPIDJMS-454) explicitly populate the durable
field if already sending a Header section
[ https://issues.apache.org/jira/browse/QPIDJMS-454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell resolved QPIDJMS-454.
------------------------------------
Resolution: Fixed
> explicitly populate the durable field if already sending a Header section
> -------------------------------------------------------------------------
>
> Key: QPIDJMS-454
> URL: https://issues.apache.org/jira/browse/QPIDJMS-454
> Project: Qpid JMS
> Issue Type: Improvement
> Components: qpid-jms-client
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Priority: Trivial
> Fix For: 0.42.0
>
>
> Once it becomes necessary to actually send a Header section for a non-persistent message, e.g. because a later priority/ttl/etc field is set, populate its durable field false explicitly since defaulting it no longer nets a strict benefit.
> (The existing 0.41.0 behaviour is perfectly legal and NOT a bug, but restoring this behaviour of <=0.11.1 will help people upgrading from <=0.11.1 to a 0.20.0+ release avoid hitting AMQ-7189 in ActiveMQ 5 releases prior to 5.15.10, which is not yet released at time of writing. More background:
> [https://lists.apache.org/thread.html/cf8d0f0ca6b232a8a447d984b27edc0fe58a7cc2e5a76f8c7e5e6cca@%3Cusers.qpid.apache.org%3E])
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org