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

Chuck Rolke resolved QPID-4268.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 0.19

Fixed with r1382095
                
> C++ Broker needs Acl support for limiting on-disk store
> -------------------------------------------------------
>
>                 Key: QPID-4268
>                 URL: https://issues.apache.org/jira/browse/QPID-4268
>             Project: Qpid
>          Issue Type: Bug
>          Components: C++ Broker
>    Affects Versions: 0.18
>            Reporter: Chuck Rolke
>            Assignee: Chuck Rolke
>             Fix For: 0.19
>
>
> The C++ Broker currently has Acl support for limiting the in-memory size of a 
> queue and the maximum number of messages that the queue may contain.
> When creating a queue a user may specify options qpid.max_size and 
> qpid.max_count. Acl support exists to specify properties:
>   queuemaxsizeupperlimit,  queuemaxsizelowerlimit,
>   queuemaxcountupperlimit, queuemaxcountlowerlimit
> to constrain the bounds of a queue that a user may create.
> This jira issue adds similar support for options qpid.file_size and 
> qpid.file_count. The Acl support shall add properties:
>   filemaxsizeupperlimit,  filemaxsizelowerlimit,
>   filemaxcountupperlimit, filemaxcountlowerlimit
> to similarly constrain the file store settings.
> This jira does NOT add new options to queue creation. Tool qpid-config 
> already specifies these options and the broker and store process them. The 
> jira simply provides a method for administrators to constrain users file 
> settings.

--
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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to