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" <andrew.grisso...@outlook.com> > To: users@qpid.apache.org > 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: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
