I believe you said that PFC kicked in based on the per-destination limit without setting ProducerWindowSize; is that accurate? If so, I'm assuming it was whole-connection PFC. If you wanted per-producer PFC, I expect you would need to set ProducerWindowSize, though I've never run with batches and had never heard of ProducerWindowSize before you mentioned it, so I'm relying heavily on what you've told me about both and don't claim any direct personal knowledge of either subject.
So the question is, do you need per-producer PFC, or is whole-connection PFC good enough for what you need? If you need per-producer PFC, I expect you'll need to set ProducerWindowSize. If you're going to try to do that, I'd recommend setting up a test with two producers who share the same connection and publish to different destinations at different rates, to prove to yourself that what's kicking in is whole-connection PFC. (It's whole-connection PFC if both producers are throttled even though only one has hit its per-destination limit. It's per-destination PFC if the other producer's destination keeps enqueuing messages.) On Aug 26, 2015 6:57 PM, "jamesTheCruncher" <ja...@mcruncher.com> wrote: > Hi Tim, > > Yes it's kicking in for the per-destination limit. > It will be great if you can edit the PFC wiki. > But just one question. > Is ProducerWindowSize still relevant? > > > > -- > 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--tp4701204p4701430.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
