Mailing-List: contact users-help@qpid.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@qpid.apache.org
Received-SPF: pass (athena.apache.org: domain of lefthandmagic@gmail.com
 designates 209.85.216.42 as permitted sender)
MIME-Version: 1.0
Date: Tue, 11 Oct 2011 15:44:33 -0700
Message-ID: 
 <CAEqX17NerTRsGjAtmYjbVCqDbmAj6r10aC50Zhk3W-Jn_-oweQ@mail.gmail.com>
Subject: Java Broker with DerbyMessageStore running out of memory with 20K
 Queues
From: Praveen M <lefthandmagic@gmail.com>
To: users@qpid.apache.org
Content-Type: multipart/alternative; boundary=0016e64b1d56ba96f404af0da61d

--0016e64b1d56ba96f404af0da61d
Content-Type: text/plain; charset=ISO-8859-1

Hi,

I'm an apache qpid newbie and am trying to benchmark Qpid Java Broker to see
if it could be use for one of my usecase.

My UseCase requires the ability to create atleast 20K persistent queues and
have them all running in parallel.

I am using the DerbyMessageStore as I understand that the default
MemoryMessageQueue is not persistant across broker restarts.

I'm running the broker with a heap of 4GB and options QPID_OPTS set to
-Damqj.read_write_pool_size=32 -Dmax_prefetch=1


My test does the following:

1) Creates a queue and registers a listener on that queue. I do this upto
20K times for 20K distinct queues. I create the queues with the following
option
    create: always , node : {type : queue, durable : true}}
    - this step goes quite fine.  I was monitoring the memory usage during
this step and it almost always stayed stable around 500-800MB
2) I produce messages for the queues (one message for each queues) and the
messages are consumed by the registered handlers in step 1.
    - When this step starts, the memory usage just shoots up and exhausts my
4GB memory all together.


Can someone please help me explaining why I am seeing this kind of a
behavior?

Also, Can you please point out if I'm missing some setting or doing
something completely wrong/stupid?


Thanks,
-- 
-Praveen

--0016e64b1d56ba96f404af0da61d--