Hi all,
I was investigating a high cpu load issue (300%, Load average 12) with my servers and after enabling the debug logging I started to see thousands of lines like the following in the logs even on a dev environment with very few messages going through the system:
2014-09-17T17:09:27-07:00 activemq: severity=DEBUG datetime=2014-09-17 17:09:27,600 thread=ActiveMQ NIO Worker 30119 category=org.apache.activemq.broker.jmx.ManagementContext Unregistering MBean org.apache.activemq:type=Broker,brokerName=dev.broker.com,destinationType=Queue,destinationName=Consumer.service.VirtualTopic.dev.data,endpoint=Consumer,clientId=ID_app1.dev.com-50108-1410983559768-0_2,consumerId=ID_app1.dev.dom-50108-1410983559768-1_1_158_401
What is "Unregistering MBean" and why does it seems related to JMX ? JMX is enabled mostly for debugging and monitoring, we have a tool that gets statistics every 15seconds.
I have the "Unregistering MBean" log only with a few clients and I think they all use Camel 2.11
Any ideas as to why this is happening?
ActiveMQ 5.9.1 + master/slave
Thanks,
Pierre-Luc
I was investigating a high cpu load issue (300%, Load average 12) with my servers and after enabling the debug logging I started to see thousands of lines like the following in the logs even on a dev environment with very few messages going through the system:
2014-09-17T17:09:27-07:00 activemq: severity=DEBUG datetime=2014-09-17 17:09:27,600 thread=ActiveMQ NIO Worker 30119 category=org.apache.activemq.broker.jmx.ManagementContext Unregistering MBean org.apache.activemq:type=Broker,brokerName=dev.broker.com,destinationType=Queue,destinationName=Consumer.service.VirtualTopic.dev.data,endpoint=Consumer,clientId=ID_app1.dev.com-50108-1410983559768-0_2,consumerId=ID_app1.dev.dom-50108-1410983559768-1_1_158_401
What is "Unregistering MBean" and why does it seems related to JMX ? JMX is enabled mostly for debugging and monitoring, we have a tool that gets statistics every 15seconds.
I have the "Unregistering MBean" log only with a few clients and I think they all use Camel 2.11
Any ideas as to why this is happening?
ActiveMQ 5.9.1 + master/slave
Thanks,
Pierre-Luc