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 21:26:23 GMT


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


jimmymartin wrote:
> 
> Dan,
> 
> I'm using the default producer flow control values. We are also polling
> for messages using 
> 
> MessageConsumer.receive() 
> 
> rather than have the broker push messages to the consumer. Does the
> jms.prefetchPolicy.queuePrefetch parameter still apply? Perhaps this is
> slowing us down?
> 
> -Jimmy
> 
> 
> Dan Tran wrote:
>> 
>> Sound like you have the classical slow consumer fast producer problem. 
>> Read up on producer flow control feature, prefetchSize, etc.
>> 
>> -Dan
>> 
>> 
> 
> 

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


Mime
View raw message