On 02/15/2012 09:23 PM, Pavel Moravec wrote:
While in Java client without ability to setup capacity, Java client
can send to the queue any further number of messages, simply ignoring
it hasn't received ACKs. Only when the client would try to close the
session or connection, it is blocked (in AUTO ACK mode) until ACKs
are received. Applying prefetch has no impact.
So the only way (I found so far) is adding session.sync() after
sending a bunch of messages. What is not ideal not only from
performance point of view.
I know there are more important issues with Java client, but is the
request of adding capacity to Java client reasonable?
Yes, I think that would be a very reasonable request.
There is a qpid.session.command_limit option that restricts the number
of outstanding commands that can be held. That is similar to the
capacity but (a) is session level rather then producer level and (b)
needs to include other AMQP 0-10 commands, not just message transfers.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
