Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: error (nike.apache.org: encountered temporary error during SPF
 processing of domain of suonayi@gmail.com)
Date: Wed, 17 Apr 2013 08:50:28 -0700 (PDT)
From: SuoNayi_Gmail <suonayi@gmail.com>
To: users@activemq.apache.org
Message-ID: <1366213828727-4665996.post@n4.nabble.com>
In-Reply-To: <1365602384133-4665807.post@n4.nabble.com>
References: <167f3ed7.fa59.13de4e2095e.Coremail.suonayi2006@163.com>
 <CAKS7T5M5ORK0rUm1pYsAd2DSsWjreudL7=+0VVSB=aDRwtyTJA@mail.gmail.com>
 <1365579246848-4665800.post@n4.nabble.com>
 <1365602384133-4665807.post@n4.nabble.com>
Subject: Re: What can be reason of 460%+ memory usage limit
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

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.