activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kevin Burton <bur...@spinn3r.com>
Subject Re: ActiveMQ 5.10 CPU spikes to 90-100% and stays there after a period of time
Date Tue, 30 Dec 2014 19:25:38 GMT
I suspect this is full GC.  Enable GC logging. You might already have a
gc.log and I’d take a look at that.  If you tail -F the file and you’re
seeing constant “Full GC” back to back at like 1 second apart you’re in a
GC storm and you need to increase your memory.

I *suspect* there’s a memory leak somewhere.  If I stop all my clients
ActiveMQ never recovers.  Either that or all the clients are using up
resources and the broker can’t release them since it spends all its time
doing full GCs.

I’m not sure this is the case for you though but I suspect it is…

On Tue, Dec 30, 2014 at 12:52 AM, ryan segura <ryan332211@hotmail.com>
wrote:

> For reasons that I cannot figure out the ActiveMQ broker will spike its CPU
> to 90-100% and stay there.  I can kill the broker and restart the process
> (consumers will then reconnect) and it works fine again with low CPU
> utilization (0-1%).
>
> How can I troubleshoot this?  There are hundreds of consumers and thousands
> of topics.  I wish there was some easy way for me to know what consumer or
> topic or queue is hogging all of the CPU.  How do people troubleshoot these
> problems?  As it is right now I feel very blind to this process.
>
> Any guidance or assistance is appreciated.  Thank you.
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/ActiveMQ-5-10-CPU-spikes-to-90-100-and-stays-there-after-a-period-of-time-tp4689332.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>



-- 

Founder/CEO Spinn3r.com
Location: *San Francisco, CA*
blog: http://burtonator.wordpress.com
… or check out my Google+ profile
<https://plus.google.com/102718274791889610666/posts>
<http://spinn3r.com>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message