[
https://issues.apache.org/jira/browse/AMQ-5735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-5735.
-----------------------------
Resolution: Fixed
resolved in http://git-wip-us.apache.org/repos/asf/activemq/commit/eb6c0826
the removeInfo was working off of 0 in error, which was the root cause of many
of the broken tests. the last sequenceId is now propagated as expected
> increment redeliverCounter in the absence of client supplied information
> ------------------------------------------------------------------------
>
> Key: AMQ-5735
> URL: https://issues.apache.org/jira/browse/AMQ-5735
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker, JMS client
> Affects Versions: 5.11.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Labels: redelivery
> Fix For: 5.12.0
>
>
> A consumer remove info contains the lastDeliveredSequenceId the consumer has
> delivered. In the absence of this information, for example when the consumer
> does a system exit or the connection drops - this information will be lost.
> The broker should increment redelivery to reflect the delivery attempt.
> Currently lastDeliveredSequenceId==0 indicates missing information but that
> ignores the fact that the messageid broker sequence could be 0. A value of -1
> should indicate nothing was delivered, > -1 the last sequence and from the
> broker side, -2 indicating that the broker provided the information and
> redelivery should be incremented. ie; -2 covers the client abort case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
