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 2017/10/25 13:57:00 UTC

[jira] [Commented] (AMQ-6849) Support a virtual topic discard mode for full consumer queues

    [ https://issues.apache.org/jira/browse/AMQ-6849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16218662#comment-16218662 ] 

ASF subversion and git services commented on AMQ-6849:
------------------------------------------------------

Commit 6da08b245e8b5c728d2fb0795ad922ccc99baf41 in activemq's branch refs/heads/master from [~gtully]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=6da08b2 ]

[AMQ-6849] provide a virtualTopic dropOnResourceLimit attribute, default to false.

Enabling will allow dispatch to continue even when end to some consumer queues
fail due to resource constraints.
The existing systemUsage sendFailIfNoSpace and sendFailIfNoSpaceAfterTimeout are
promoted to destination policy options allowing selective destinations to fail a
send with an exception. The global system usage options are still in place.
When dropOnResourceLimit=true dispatch will continue in the event that any
subscription queue throws a resource limit exception on send failure.


> Support a virtual topic discard mode for full consumer queues
> -------------------------------------------------------------
>
>                 Key: AMQ-6849
>                 URL: https://issues.apache.org/jira/browse/AMQ-6849
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 5.15.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>             Fix For: 5.16.0
>
>
> For regular topics, the slow consumer problem has a few solutions via the [discarding policies|http://activemq.apache.org/slow-consumer-handling.html]
> For Virtual Topics, message expiry is the only viable option, however dispatch will be blocked till expiry kicks in. In the same way that we can discard some messages for a slow topic subscriber it can make sense to discard messages for a subscriber queue that is full such that dispatch to fast queues can continue.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)