Hi Tim, Thanks for your continued interest in this subject. Yes, as per my testing, I didn't configure any ProducerWindowSize but found that the PFC was kicking in based on the per-destination limit I configured. I don't think it was the whole-connection PFC because I had set fairly larger limits for system usage. >From the logs, I found that the parent usage didn't hit even 1 percentage.
But I noticed that the "Producers will be throttled" message was immediately followed by "Producer stopped" in the logs, which makes me to think that one should configure a ProducerWindowSize value that is less than the per-destination limit set. Eventhough the Producer was not stopped immediately in my case, I found that the Producer was stopped eventually after testing it for a prolonged period of time (> 8 hours). I will configure ProducerWindowSize and continue my testing. But it will be great if someone can tell whether my "guessing" is correct and whether I am proceeding in the right direction. -- 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--tp4701204p4701571.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
