I took a look at the examples and that works just like I wanted, I'm not sure 
how my googling missed that page.  
I also saw that I can have the queue be auto-deleted after a certain time 
period, but it does not seem to work when I make the queues durable. For 
example:
my-topic; {link:{durable:True, name:'my-subscription', 
x-declare:{auto-delete:True, arguments:{'qpid.auto_delete_timeout':30}}}}

In this case I see durable in qpid-config.  If I remove durable:True, I see 
auto-delete.  Is this the expected behavior and if it is, is there a way to 
have the broker automatically delete a durable subscription queue after a 
certain period of time?
Thanks
> Date: Fri, 18 Oct 2013 07:12:30 -0400
> From: [email protected]
> To: [email protected]
> Subject: Re: Flow Control for JMS Durable Subscribers
> 
> Hi Andrew,
> I recommend reading 
> https://cwiki.apache.org/confluence/display/qpid/Addressing+Examples where 
> one example covers your requirement. When declaring the topic, use 
> "{link:{x-declare:{arguments:{'qpid.max_count':500,'qpid.policy_type':'ring'}}}}"
>  in its address string to create auxiliary queue of ring policy and of 
> maximal message depth 500.
> 
> Kind regards,
> Pavel
> 
> 
> ----- Original Message -----
> > From: "Andrew Grissom" <[email protected]>
> > To: [email protected]
> > Sent: Thursday, October 17, 2013 11:19:41 PM
> > Subject: Flow Control for JMS Durable Subscribers
> > 
> > I have a Java client using the JMS interfaces that connects to the qpid C++
> > broker to receive updates on a topic.   I need to make this subscription
> > durable, which is pretty easy using the straight JMS calls.  However, the
> > problem I have is how do I handle clients that do not cleanly remove their
> > subscriptions or do not connect for an extended period of time?  I can
> > prevent this somewhat by using the TTL values but is there a way to switch
> > the broker from rejecting messages when a queue is full to using the ring
> > policy?  Is there a better way to handle this situation?
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 
                                          

Reply via email to