activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (AMQ-6361) Message can remain inflight after consumer side expiration acknowledgements
Date Fri, 22 Jul 2016 14:19:20 GMT


ASF subversion and git services commented on AMQ-6361:

Commit 6cc2c1190da15579a9a886bad03596e14a77a677 in activemq's branch refs/heads/master from
[;h=6cc2c11 ]

AMQ-6361 - fix contention over expiry processing with expiry task and client expiry ack, unit
test regression sorted.

> Message can remain inflight after consumer side expiration acknowledgements
> ---------------------------------------------------------------------------
>                 Key: AMQ-6361
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.13.3
>            Reporter: Timothy Bish
>            Assignee: Gary Tully
>             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)
> 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

View raw message