The "target" capacity was meant for producer flow control which was never implemented. The "source" capacity is used as message credits for the subscription.
However flow control is controlled at the session level. That is the unacked messages for the session is taken into account when issuing completions (which effectively restores credits). What should really happen is a way to track this on a per subscription basis. There is an open bug report for this. Note if capacity is not specified, we use the value of max_prefetch as the number of message credits. Regards, Rajith On Thu, Jul 26, 2012 at 5:36 PM, Harry.alto <[email protected]> wrote: > Hi , > I am using C++ Qpid Broker(MRG 0.14) and Java JMS client. > I understand from the QPID documentation and google resources that we can > set the consumer capacity which effectively works at session level rather > than consumer level in Java. > Please let me know what does the source and target mean in the capacity. I > tried google but > couldn't find info. > > "ADDR:my-queue; {create: always, link:{capacity: {source:10, target:15} }} > > Thanks in Advance. > Harry > > > > > -- > View this message in context: > http://qpid.2158936.n2.nabble.com/In-Consumer-Flow-Control-what-does-source-and-target-means-tp7580271.html > Sent from the Apache Qpid users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
