I should follow up with some of my results. I did resolve the OOM issue by
setting the thread size (-Xss) in the JVM to 128k. I was able to ramp up to
6k concurrent connections without any trouble at all. I was testing
scalability and fail over and was able to fail over these connections to
ano
Have you considered pooling the connections? You'll probably find the
performance of any Java app will degrade with that many threads...
Ken Ringdahl wrote:
>
> I'm running a load test that intends to throw on the order of several
> thousand connections at a 2 node broker system with failover
For the past 2 weeks we have been testing ActiveMQ to answer this question
ourself. Here is what we found.
Creating a Connection takes one thread.
Creating a Session takes one thread.
Creating a NON Persisted Topic with a messageListner takes one thread, when
the topic is no longer used the thre
if you look at the message
java.lang.OutOfMemoryError: unable to create new native thread
this will tell you that it has nothing to do with your Xmx setting.
Threads and thread stacks are allocated outside your Java heap (ie, your Xms and Xmx settings)
and you've simply run out of space to cre
