[
https://issues.apache.org/jira/browse/QPID-8067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16348969#comment-16348969
]
Keith Wall commented on QPID-8067:
----------------------------------
Changes look reasonable, ported to the 7.0.x branch.
> [Broker-J] Default queue filter for arrival time with non-zero replay period
> does not filter messages as documented
> -------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-8067
> URL: https://issues.apache.org/jira/browse/QPID-8067
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
> Affects Versions: qpid-java-6.0.8, qpid-java-broker-7.0.0, qpid-java-6.1.5
> Reporter: Alex Rudyy
> Assignee: Alex Rudyy
> Priority: Minor
> Fix For: qpid-java-broker-7.0.1, qpid-java-broker-7.1.0
>
>
> As per Broker documentation the replay period in arrival filter determines a
> time interval ( in seconds) for which the arriving messages enqueued into
> queue within given interval before consumer attach have to be delivered to
> the consumer. Thus, all message on the queue with arrival time greater than
> ({{consumer attach time}} - {{replay period}}) should be delivered to the
> consumer. If filter is specified on consumer attach, the delivery works as
> expected. However, if arrival filter is specified as default queue filter,
> the broker behaviour is not documentation compliant:
> * the broker delivers to consumer only messages with arrival time greater
> than ({{consumer attach time}} + {{replay period}})
> * the {{replay period}} is treated as being set in milliseconds rather than
> in seconds
> The issue only impacts use cases when arrival filter with non-zero {{replay
> period}} is set as queue default filter.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
