You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2016/07/15 20:46:20 UTC
[jira] [Commented] (AMQ-6336) QueueBrowser delivers expired
messages
[ https://issues.apache.org/jira/browse/AMQ-6336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15380081#comment-15380081 ]
ASF subversion and git services commented on AMQ-6336:
------------------------------------------------------
Commit a3a5a1affa7aa229202efc51625531ccce1414bb in activemq's branch refs/heads/master from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=a3a5a1a ]
https://issues.apache.org/jira/browse/AMQ-6336
Ensure that when expired messages are handled client side that pull
consumers get a chance to see it and send a new pull request complete an
outstanding timed pull.
> QueueBrowser delivers expired messages
> --------------------------------------
>
> Key: AMQ-6336
> URL: https://issues.apache.org/jira/browse/AMQ-6336
> Project: ActiveMQ
> Issue Type: Improvement
> Affects Versions: 5.13.3
> Reporter: Dejan Bosanac
> Assignee: Timothy Bish
> Fix For: 5.14.0
>
>
> With [AMQ-5340] we started sending expired messages from the broker to the browser consumer to speed up browsing when there's expired messages on the queue. We should try to keep the old behaviour by checking for expired messages on the client side.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)