activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dan Tran <dant...@gmail.com>
Subject Re: ava.lang.OutOfMemoryError: Failed to fork OS thread - 5.2.0 broker
Date Tue, 06 Oct 2009 22:45:24 GMT

Jimmy,

You may want to run with Sun JVM and hookup Jconsole to find out what is
going on with your JVM.

-D


jimmymartin wrote:
> 
> Dan,
> 
> The message size is ~1500 bytes on average, 90% are 1100 bytes. The
> consumer should be very fast, up to 1000 msg/sec for each consumer with 24
> consumers pulling from a single broker. The producers are not enqueueing
> anything near that rate. Generally we are in the 50-100 msg/sec rate for
> all the producers combined.
> 
> Our configuration is pretty much the stock config. The only real change we
> have made is to turn off the dedicate task runner:
> -Dorg.apache.activemq.UseDedicatedTaskRunner=false.
> 
> Thanks for your help, 
> -Jimmy
> 
> 
> Dan Tran wrote:
>> 
>> 
>> Default flow control can nail you. how big is your message, how fast is
>> your consumer, and what is your broker configuration look like?
>> 
>> -D
>> 
>> 
> 
> 

-- 
View this message in context: http://www.nabble.com/ava.lang.OutOfMemoryError%3A-Failed-to-fork-OS-thread---5.2.0-broker-tp25774586p25777799.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message