[
https://issues.apache.org/jira/browse/AMQ-6361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-6361.
-------------------------------
Resolution: Fixed
> Message can remain inflight after consumer side expiration acknowledgements
> ---------------------------------------------------------------------------
>
> Key: AMQ-6361
> URL: https://issues.apache.org/jira/browse/AMQ-6361
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.13.3
> Reporter: Timothy Bish
> Assignee: Timothy Bish
> Fix For: 5.14.0
>
>
> If the client clock is slightly ahead of the brokers clock a message could be
> expired on the client but not considered expired on the broker.
> When the expiry ACK is sent to the broker it checks if the message is also
> considered expired on the broker side. If the broker clock is behind the
> client side clock the message could be considered not expired on the broker
> and not
> removed from the broker's dispatched list. This leaves the broker reporting a
> message inflight from the broker's perspective even though the message has
> been expired on the consumer(client) side
> The broker should treat the expired ACK as the authority on whether a message
> is expired and process it as such regardless of the broker side clock.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
