AnsweredAssumed Answered

JMX for JBOSS Datasources and WebContainers

Question asked by Lucarazzi on Mar 16, 2016
Latest reply on Mar 18, 2016 by Lucarazzi

Hello Community,

I am trying to get JMX metrics for Oracle JDBC Datasources and for WebContainer thread

I have enabled succesfully the JMX module and also got all the mbeans using the value

 

com.wily.use.platform.mbeanserver=true

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

 

But after a while I get errors like:

3/16/16 03:49:58 PM CET [DEBUG] [IntroscopeAgent.JMX Service] JMX data unavailable for JMX|jboss.as|data-source=ExampleDS|subsystem=datasources:backgroundValidationMillis, this may be a transient failure

3/16/16 03:49:58 PM CET [DEBUG] [IntroscopeAgent.JMX Service] JMX data unavailable for JMX|jboss.as|data-source=ExampleDS|subsystem=datasources:idleTimeoutMinutes, this may be a transient failure

3/16/16 03:49:58 PM CET [DEBUG] [IntroscopeAgent.JMX Service] JMX data unavailable for JMX|jboss.as|data-source=ExampleDS|subsystem=datasources:blockingTimeoutWaitMillis, this may be a transient failure

3/16/16 03:49:58 PM CET [DEBUG] [IntroscopeAgent.JMX Service] JMX data unavailable for JMX|jboss.as|data-source=ExampleDS|subsystem=datasources:useTryLock, this may be a transient failure

3/16/16 03:49:58 PM CET [DEBUG] [IntroscopeAgent.JMX Service] JMX data unavailable for JMX|jboss.as|data-source=ExampleDS|subsystem=datasources:preparedStatementsCacheSize, this may be a transient failure

3/16/16 03:49:58 PM CET [DEBUG] [IntroscopeAgent.JMX Service] JMX data unavailable for JMX|jboss.as|data-source=ExampleDS|subsystem=datasources:minPoolSize, this may be a transient failure

3/16/16 03:49:58 PM CET [DEBUG] [IntroscopeAgent.JMX Service] JMX data unavailable for JMX|jboss.as|data-source=ExampleDS|subsystem=datasources:maxPoolSize, this may be a transient failure

3/16/16 03:49:58 PM CET [DEBUG] [IntroscopeAgent.JMX Service] JMX data unavailable for JMX|jboss.as|data-source=ExampleDS|subsystem=datasources:allocationRetryWaitMillis, this may be a transient failure

 

Do you know how to solve the issue or at least the name of the bean to monitor?

Thanks

 

Luca Razzi

Outcomes