qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pavel Moravec <pmora...@redhat.com>
Subject Re: Flow Control for JMS Durable Subscribers
Date Fri, 18 Oct 2013 11:12:30 GMT
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

Kind regards,

----- Original Message -----
> From: "Andrew Grissom" <andrew.grissom99@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-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org

View raw message