I think you might be right. Is there a way to monitor when ActiveMQ runs out
of memory? What could be some of the reasons it would run out of memory?
bsnyder wrote:
>
> On Tue, Jul 8, 2008 at 8:20 AM, sparky2708 <[EMAIL PROTECTED]> wrote:
>>
>> I am noticing that services connected to an ACTIVEMQ Broker stop
>> receiving
>> messages all of a sudden. I don't see anything in any of the ACTIVEMQ
>> logs.
>> I am using ActiveMQ 5.1.0. How can I figure out what is going on? (I have
>> a
>> suspicion that the broker might stop sending messages maybe because the
>> consumer is too slow, or not acknowledging correctly... not sure). How
>> can I
>> drill into what the broker is thinking?
>
> It could be a slow consumer situation, but it sounds to me like the
> broker may have reached the limit of the memory it has available. Try
> increasing the memoryUsage to something higher than the default
> setting in the conf/activemq.xml file. Below is an example:
>
> <memoryUsage>
> <memoryUsage limit="256 mb"/>
> </memoryUsage>
>
> Bruce
> --
> perl -e 'print
> unpack("u30","D0G)[EMAIL PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
> );'
>
> Apache ActiveMQ - http://activemq.org/
> Apache Camel - http://activemq.org/camel/
> Apache ServiceMix - http://servicemix.org/
>
> Blog: http://bruceblog.org/
>
>
--
View this message in context:
http://www.nabble.com/Services-connected-to-ACTIVEMQ-stop-receiving-messages-%28ActiveMQ-5.1.0%29-tp18340354p18344215.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
