You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2012/10/02 22:57:07 UTC

[jira] [Resolved] (AMQ-4091) Allow a memory limit to be configured on a temp topic

     [ https://issues.apache.org/jira/browse/AMQ-4091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully resolved AMQ-4091.
-----------------------------

    Resolution: Fixed
      Assignee: Gary Tully

fixed in http://svn.apache.org/viewvc?rev=1393174&view=rev

{code}<policyEntry tempTopic="true" ... />{code} will now take effect.
                
> Allow a memory limit to be configured on a temp topic
> -----------------------------------------------------
>
>                 Key: AMQ-4091
>                 URL: https://issues.apache.org/jira/browse/AMQ-4091
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 5.6.0, 5.7.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>              Labels: memory, pfc, temp, topic
>             Fix For: 5.8.0
>
>
> It is currently not possible to enable producer flow control on a temp topic using a destination limit. With a regular topic is it.
> Currently, we don't apply any destination policy to temp topics. 
> We should allow setting limits to allow temp topic to be partitioned such that they don't consumer all resources.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira