hmm... could be but I am definitely not sure what is actually causing it, what is interesting and I've forgot to mention is that i have large number of still hanging connections and basically it blocks producers for some period as rule of thumb. However, I was not able to reproduce this problem on a small number of producers/consumers. Just stopping the producers doesn't help and it can be reproduced on relatively small number of messages being sent to the queue (1000-2000) and I don't experience this problem if I connect consumers after some time (about 10k messages), but what really blocks it is situation when I kill the consumers... I assume that it could be related to hanging connections, but the problem is that sometimes broken connections stay present after a very long period of time (at least with bstat I can see large number of Type = Subscription elements, that exceeds the connected producers/subscribers if that's of any relevance).
Thanks, Igor On 6/21/06, Hiram Chirino <[EMAIL PROTECTED]> wrote:
When you stop a consumer I wonder if your causing a slow consumer situation... see: http://activemq.com/site/slow-consumers.html On 6/21/06, Igor Bogicevic <[EMAIL PROTECTED]> wrote: > Hi all, > > I've been testing ActiveMQ under relatively high load and number of > producers and consumers (50-100 on each side) and I've attached the > code that I have been using for test purposes (it's not really clean > code since it's used for testing purposes only). What happens is when > I launch about 50-60 consumers/producers (they run on a different > boxes) and I start to stop consumer processes, producers tend to block > for a shorter period, if I repeat this process for a while I get to > state where's a whole queue blocked for 1-2h or longer (sometimes for > good). > Is this general performance problem with ActiveMQ or am I doing something wrong? > > Thanks, > Igor > > > -- Regards, Hiram Blog: http://hiramchirino.com
