Now I get fully understand why the remote slow consumer can block the producer. What I missed is that messages sent from the producer will pass throght the virtual topic as well even if the topic is virtual but it does exist in the physical form in the broker, b/w PFC is enabled for topics and the memory is exhausted b/w unreasonable memory usage limit configuration for queues, the producer gets blocked in the topic eventually.So I can see the phenomenon once the slow consumer enqueues 200 messages the producer can resume to send 200 messages. There is some room to optimize the send logic in the topic,such as we can first check if there are consumers on the topic, if not we can just return and do nothing anymore, so that the producer wont get blocked.
-- View this message in context: http://activemq.2283324.n4.nabble.com/What-can-be-reason-of-460-memory-usage-limit-tp4665651p4665996.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
