AnsweredAssumed Answered

JMX MBean Server Error in Java Agent Log

Question asked by dxsmith12 on Dec 7, 2016
Latest reply on Dec 11, 2016 by Hallett_German
Branched to a new discussion

I wanted to throw this out there to see if anyone has seen this issue before.  We have a set of Jboss application servers for which we get no jmx metrics.   I set my log level to DEBUG and captured the debug message below.  There is a runtime exception loading the MBean server, specifically a ClassNotFoundException.

 

My question:  Since this is being logged within the APM java agent log, is it something we may have misconfigured within the agent profile?  I see no analogous errors in the Jboss server log pertaining to JMX mbeans.

 

Any insight on how to attack this issue would be appreciated.

 

Thanks

 

 

 

#######################################################

 

Log info:

 

12/07/16 02:03:36 PM EST [INFO] [IntroscopeAgent.Agent] Activating JMX Data Collection

 

12/07/16 02:03:41 PM EST [INFO] [IntroscopeAgent.Agent] Using the following JMX Primary Keys:

 

12/07/16 02:03:41 PM EST [INFO] [IntroscopeAgent.Agent] Using the following JMX Filter Keys: jboss*service=invoker*type=pooled,jboss*service=TransactionManager,jboss.j2ee*plugin=pool,jboss*plugin=cache,jboss.jca*service=ManagedConnectionPool,jboss.jca*service=WorkManagerThreadPool,jboss.mq*service=DestinationManager,jboss.mq*service=MessageCache,jboss.mq*service=PersistenceManager,jboss.mq.destination*service=Queue,jboss.mq*service=Topic,jboss.system*service=ThreadPool,jboss.system*type=ServerInfo,jboss.web*type=Cache,jboss.web*type=Manager,jboss.web*type=GlobalRequestProcessor,jboss.web*type=ThreadPool

 

12/07/16 02:03:41 PM EST [DEBUG] [IntroscopeAgent.Agent] Unable to handle Connection class by name : org.jboss.jca.adapters.jdbc.jdk6.WrappedConnectionJDK6

 

12/07/16 02:03:41 PM EST [DEBUG] [IntroscopeAgent.Agent] Unable to handle Connection class by name : org.jboss.jca.adapters.jdbc.jdk6.WrappedConnectionJDK6

 

12/07/16 02:03:41 PM EST [INFO] [IntroscopeAgent.Agent] Lookup and use the platform MBeanServer instead of creating a new one                                    (com.wily.use.platform.mbeanserver) set to default value of "false"

 

12/07/16 02:03:41 PM EST [ERROR] [IntroscopeAgent.Agent] Failed to activate JMX data collection

 

12/07/16 02:03:41 PM EST [DEBUG] [IntroscopeAgent.Agent] javax.management.JMRuntimeException: Failed to load MBeanServerBuilder class org.jboss.as.jmx.PluggableMBeanServerBuilder: java.lang.ClassNotFoundException: org.jboss.as.jmx.PluggableMBeanServerBuilder

        at javax.management.MBeanServerFactory.checkMBeanServerBuilder(MBeanServerFactory.java:503)

        at javax.management.MBeanServerFactory.getNewMBeanServerBuilder(MBeanServerFactory.java:539)

        at javax.management.MBeanServerFactory.newMBeanServer(MBeanServerFactory.java:316)

        at javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:231)

        at com.wily.introscope.agent.jmx.JMXService.IAgentService_startService(JMXService.java:115)

        at com.wily.introscope.agent.service.ServiceAdministrator$ServiceInitializer.startService(ServiceAdministrator.java:550)

        at com.wily.introscope.agent.service.ServiceAdministrator.registerServiceSync(ServiceAdministrator.java:331)

        at com.wily.introscope.agent.webappsupport.AWebAppSupportReflectionDelegatingService.IAgentService_startService(AWebAppSupportReflectionDelegatingService.java:75)

        at com.wily.introscope.agent.service.ServiceAdministrator$ServiceInitializer.startService(ServiceAdministrator.java:550)

        at com.wily.introscope.agent.service.ServiceAdministrator$ServiceInitializer.startServiceSafe(ServiceAdministrator.java:564)

        at com.wily.introscope.agent.service.ServiceAdministrator$ServiceInitializer.IExecutableItem_execute(ServiceAdministrator.java:428)

        at com.wily.util.task.AsynchExecutionQueue$WrapperItem.IExecutableItem_execute(AsynchExecutionQueue.java:414)

        at com.wily.util.task.AsynchExecutionQueue.doTask(AsynchExecutionQueue.java:205)

        at com.wily.util.task.ATask$CoreTask.run(ATask.java:132)

        at java.lang.Thread.run(Thread.java:745)

Caused by: java.lang.ClassNotFoundException: org.jboss.as.jmx.PluggableMBeanServerBuilder

        at java.net.URLClassLoader.findClass(URLClassLoader.java:381)

        at com.wily.util.extension.JarExtension$AllPermissionsClassLoader.findClass(JarExtension.java:278)

        at java.lang.ClassLoader.loadClass(ClassLoader.java:424)

        at java.lang.ClassLoader.loadClass(ClassLoader.java:357)

        at javax.management.MBeanServerFactory.loadBuilderClass(MBeanServerFactory.java:446)

        at javax.management.MBeanServerFactory.checkMBeanServerBuilder(MBeanServerFactory.java:488)

 

12/07/16 02:08:51 PM EST [WARN] [IntroscopeAgent.Agent] Heartbeat: Agent, Behavior: Introscope JMX Protocol Adaptor has been running for excessively long time (105834 ms).

Outcomes