Mailing-List: contact users-help@qpid.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@qpid.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <CAAG0USd4Wm=s-k8POv1C3QoS-BW8zaDUiE8HQoEzzozSs3Kf-Q@mail.gmail.com>
References: 
 <CAAG0USd4Wm=s-k8POv1C3QoS-BW8zaDUiE8HQoEzzozSs3Kf-Q@mail.gmail.com>
Date: Tue, 18 Dec 2012 09:01:20 +0100
Message-ID: 
 <CAOhBXQ63=zA=Tm1m_2Vrcf9B3+xwpD-3v7TK9RpGX7GXMLmL6Q@mail.gmail.com>
Subject: Re: limit policy on bound temporary queues
From: Jakub Scholz <jakub@scholz.cz>
To: users@qpid.apache.org
Content-Type: multipart/alternative; boundary=089e0122896c363ed604d11be746

--089e0122896c363ed604d11be746
Content-Type: text/plain; charset=ISO-8859-1

Hi Lance,

>From the client you can use address similar to this to create and temporary
ring type queue:

queue_1;
{
    create: receiver,
    assert: never,
    node:
    {
        type: queue,
        x-declare:
        {
            auto-delete: true,
            exclusive: false,
            arguments:
            {
                'qpid.policy_type': ring,
                'qpid.max_count': 1000,
                'qpid.max_size': 1000000
            }
        },
        x-bindings:
        [
            {
                exchange: 'exchange_1',
                queue: 'queue_1',
                key: 'routing_key_1'
            }
        ]
    }
}

This creates the auto-delete ring type queue named queue_1 with capacity
for 1000 messages or 1000000 bytes and binds it to the exchange named
exchange_1 suign the routing key "routing_key_1". I assume for fanout
exchange, you do not need the routing key.

If you want, you can also use ACLs to allow the clients to create only ring
type queues:

acl allow user1@QPID create  queue name=queue_*  maxqueuecount=1000
 maxqueuesize=1024000  policytype=ring durable=false autodelete=true

This rule will make the broker reject all attempts to create a queue which
doesn't fulfill all the specified options.

Regards
Jakub

On Tue, Dec 18, 2012 at 4:09 AM, Lance D. <lanced@gmail.com> wrote:

> Hello,
>
> I'm trying to figure out a problem and I'm hoping to find the right way to
> make this happen.
>
> I've got a data producer that publishes to an fanout exchange.  My system
> requires that under no circumstances can the producer get throttled because
> even if 1 user can't keep up, the other consumers need the data as soon as
> possible.  My thought is that if I just force all of the consumers to
> connect with a 'ring' limit policy, then I should be okay because slow
> consumers will just drop data on the floor.  So I'd like to be able to make
> that the default policy.
>
> That said, I'm fairly certain that isn't possible, so I'd at least like to
> setup my clients with the correct settings.  I've read through the
> documentation, but I can't seem to figure out how to register to receive
> from an exchange, using a temporary (implicit) queue.
>
> Thanks in advance for the help.
> -Lance
>

--089e0122896c363ed604d11be746--