I understand that, and I agree with you that it doesn't seem like expected behavior. My point was that I don't believe what you're seeing is specifically because of asynchronous sends, though I can't say for sure, and I gave you an easy way to test whether asynchronous sends do indeed produce the behavior you're seeing. If you do that experiment and PFC kicks in, then you know it's not the asynchronous nature of batch sends that is causing the behavior you're seeing, and if it doesn't, then you have an indication that your initial hunch was right and mine was wrong and that pursuing setting a producer window size might be worth doing after all. On Aug 19, 2015 2:03 AM, "jamesTheCruncher" <ja...@mcruncher.com> wrote:
> Hi Tim, > > Thank you very much for the detailed response. > Yes, I am aware that PFC will kick in eventually and do a collateral damage > while using async sends without configuring /Producer Window Size/. > > However, I am not seeing that collateral damage when sending messages in > batches with batch size > 1. Messages are enqueued continuously as though > PFC is turned off until the /storeUsage/ limit is reached. > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/What-is-the-correct-way-to-throttle-ActiveMQ-producers-who-send-persistent-messages-in-batches-to-a--tp4701204p4701211.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
