[
https://issues.apache.org/jira/browse/AMQ-6517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15878324#comment-15878324
]
ASF subversion and git services commented on AMQ-6517:
------------------------------------------------------
Commit 816f81e605ab692ca48d22cce30cf3722f83013f in activemq's branch
refs/heads/master from [~gtully]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=816f81e ]
[AMQ-6517] resolve intermittent test failure - wait for client connection to
see broker disconnect
> Make redelivery policy preDispatch check optional
> -------------------------------------------------
>
> Key: AMQ-6517
> URL: https://issues.apache.org/jira/browse/AMQ-6517
> Project: ActiveMQ
> Issue Type: Bug
> Components: JMS client
> Affects Versions: 5.14.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Fix For: 5.15.0
>
>
> AMQ-5146 introduced a pre dispatch check on the redelivery policy to ensure
> that a consumer the repeatidly crashed with a redelivery limit would
> eventually fail the message to the dlq.
> There are cases where this is not ideal. For example, if the redelivery
> policy denies redelivery, maxRedeliveries=0 and a message has been inflight
> on an aborted connection. Broker side the redelivery count will be
> incremented, because the broker knows it may have been delivered (on a
> connection abort, the consumer goes not get to supply accurate delivery
> status information). With the preemptive check, this message it won't get
> delivered and will instead go directly to the DLQ.
> making the preDeliveryCheck optional allows maxRedeliveries=0 to work in this
> case.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
