Hi, Based on my experience, I would assume, that if you want your customers to use RING type queues, you should anyway force it using ACL, since even when the default policy type is implemented, the consumer will be probably able to overwrite the default value. You can use
acl allow <Consumer> create queue name=<QueueName> policytype=ring BTW: It seems that the ACL property "policytype" is missing in the table 1.6 in chapter 1.5.2.1 of the "AMQP Messaging Broker (Implemented in C++)" book. Is a JIRA ticket used for the documentation changes as well? Should I enter one for this problem? Regards Jakub On Mon, May 9, 2011 at 16:48, Rajith Attapattu <[email protected]> wrote: > On Mon, May 9, 2011 at 6:36 AM, Gordon Sim <[email protected]> wrote: >> On 05/06/2011 02:34 PM, Fallon, Richard wrote: >>> >>> Hello, >>> >>> Is it possible to change some of the default settings used when a queue >>> is created, note I do not mean override them at runtime? >>> >>> So currently if a queue is created the default policy when the queue >>> size is exceeded is to block the producer so no more data arrives. This >>> is not acceptable in my system. I would like all queues that are >>> created to be created with the default policy_type of RING, so the >>> producer is never blocked. However all my queues are created >>> dynamically by the consumers using the AMQP syntax, ideally I would >>> prefer not to rely on the consumers to create the queues with a RING >>> policy. >>> >>> So what I would like is for all queues to be created at runtime to use a >>> RING policy, without having to over-ride it at runtime. Can I change >>> the default policy to be RING? >> >> Unfortunately not at present. > > I created a JIRA to track this. > https://issues.apache.org/jira/browse/QPID-3248 > > However you could probably do this by using ACL. > i.e to restrict every queue being created to the required policy of your > choice. > The added benefit here is that you could have different queue policies > by users (or groups of users). > > Let me test this out and get back to you. > > Rajith > >> --------------------------------------------------------------------- >> Apache Qpid - AMQP Messaging Implementation >> Project: http://qpid.apache.org >> Use/Interact: mailto:[email protected] >> >> > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:[email protected] > > --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
