AnsweredAssumed Answered

Re: JMX MBean Server Error in Java Agent Log (Not Seeing JMX Metrics)

Question asked by dxsmith12 on Dec 8, 2016
Latest reply on Dec 11, 2016 by Hallett_German
Branched from an earlier discussion

That setting eliminated the runtime exception in the failure to load the Mbean server.  Thanks!  However, I still get no JMX stats in WebView (as a matter of fact, the JMX node does not even appear in the Investigator under the jboss agent in-question).

 

In my log I see:


12/08/16 11:04:13 AM EST [DEBUG] [IntroscopeAgent.Agent] Checking IntervalHeartbeats.
12/08/16 11:04:13 AM EST [WARN] [IntroscopeAgent.Agent] Heartbeat: Agent, Behavior: Introscope JMX Protocol Adaptor has been running for excessively long time (159502 ms).

12/08/16 11:04:13 AM EST [DEBUG] [IntroscopeAgent.Agent] Unable to handle Connection class by name : org.jboss.jca.adapters.jdbc.jdk6.WrappedConnectionJDK6

 

My APM java agent profile has the following jmx entries:

 

introscope.agent.jmx.enable=true

 

com.wily.introcope.agent.jmx.syncWithAllMbeanServersForcibly=true

 

com.wily.use.platform.mbeanserver=true

 

introscope.agent.jmx.name.filter=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

 

Any other ideas?

Outcomes