You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by ryan segura <ry...@hotmail.com> on 2014/04/16 20:35:08 UTC
How to troubleshoot broker problems?
How do you troubleshoot broker problems?
I am running into issues where users cannot connect to the broker anymore.
But messages are still flowing (for some topics/queues).
Jconsole does not help because in this scenario it has no mbeans or just
partial mbeans of data. The broker is generally unhealthy.
How do you find the cause of these problems and start troubleshooting?
If I restart the broker everything is fine for a day or two if I am lucky.
--
View this message in context: http://activemq.2283324.n4.nabble.com/How-to-troubleshoot-broker-problems-tp4680369.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: How to troubleshoot broker problems?
Posted by Gary Tully <ga...@gmail.com>.
increase the logging level (log4j) so there will be some indication of
problems in the trace or debug messages.
Get a series of thread dumps to see if any threads are blocked.
ensure the os is ok, as in no file descriptor or memory of file
system limits are exceeded.
On 16 April 2014 19:35, ryan segura <ry...@hotmail.com> wrote:
> How do you troubleshoot broker problems?
>
> I am running into issues where users cannot connect to the broker anymore.
> But messages are still flowing (for some topics/queues).
>
> Jconsole does not help because in this scenario it has no mbeans or just
> partial mbeans of data. The broker is generally unhealthy.
>
> How do you find the cause of these problems and start troubleshooting?
>
> If I restart the broker everything is fine for a day or two if I am lucky.
>
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/How-to-troubleshoot-broker-problems-tp4680369.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
--
http://redhat.com
http://blog.garytully.com