Exposing JMX datasource metrics in JBOSS 6.4

[David Richards]

Hi - does anyone know how to expose all the datasource metrics available in JBOSS 6.4 (Domain/Host controller build)

 

Our APM agent is at v9.5.5

OS is Red Hat Linux

 

In the agent profile we have set

 

introscope.agent.jmx.enable=true

introscope.agent.jmx.ratecounter.enable=true

introscope.agent.jmx.name.filter=

 

We want to see the active datasource connection count, but all we get back is the min/max count.

 

Any ideas from the community as to how to get that data ?

 

[David Lewis]

Hi Dave,

We saw something in JBoss EAP 6.3.3, I'm not sure if it's relevant, it isn't exactly the same behaviour but might be useful..

http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec1119973.aspx

 

Can you compare the output in another tool like JConsole to see if the JMX output is different there ?

 

Thanks,

David

[Hallett German]

Hi Dave:

Please let us know if what Dave suggested is helpful or addition follow-up is needed.

 

Thanks

Hal German

[David Richards]

Hi - we don't have access to JConsole so I cant try that.

 

We have identified the xsd file and made the change outlinied.

 

However, no extra metrics are being reported. We particularly want to see active count. Any idea how to expose that ?

 

[David Lewis]

HI Dave,

This is, as far as I'm aware, the JMX reference for Jboss EAP 6.4 which does point to the particular metric I think..

 

Wildfly Model Reference

 

In terms of Introscope config:

 

This is the other main property specifically for getting JMX data out of Jboss:

 

 

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

 

as well as this if you haven't specified it:

 

 

com.wily.use.platform.mbeanserver=true

 

You would have to add it into the agent profile.

It will probably increase CPU usage on the machine

 

It's difficult for us to provide any configuration if the data is not even being published, that's why we have to ask to verify in JConsole because if the data isn't there either, then the data is simply not available, in which case Red Hat would have to help further.

 

I'm trying to find a different way to verify the JMX output directly on the command line, where there is no GUI on the remote machine and we can't get around it, I would normally export the display to my Windows machine running XMing (other solutions are available) and look at it from there..

 

Thanks,

David

[David Richards]

Hi Dave, tried that but no difference in terms of metrics being gathered.

 

This is what I have got set now in the profile for JMX........

 

introscope.agent.jmx.enable=true

introscope.agent.jmx.name.filter=jboss.as|data-source*,jboss.as|deployment*

#introscope.agent.jmx.name.filter=

introscope.agent.jmx.excludeStringMetrics=true

com.wily.use.platform.mbeanserver=true

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

 

From the Wildfly link you suppied it's a bit weird as can't see "maxPoolSize" or "minPoolSize" defined there yet we are getting those metrics.

[David Lewis]

Hi Dave,

If you go up a little bit in the Wildfly model to here,

 

Wildfly Model Reference

 

this points you to what you can expect to see directly under the datasource name, which is where those values are reported in the JMX tree structure.

 

the max and min pool size are there under the attributes with data type Integer. There are other Integer values not showing admittedly but that is where it is coming from.

 

Thanks,

David

[David Richards]

Has anyone from the APM community (or CA labs) managed to get meaningful JMX datasource metrics out from JBOSS EAP ? Just wondering if there are any sample config we can look at to try.

[Hallett German]

DavidLewis

Hi Dave:

  David's last note #6 provided a possible research resource. Having gone back and forth several times, opening a case may be the next step

 

Thanks

Hal German

[David Richards]

OK I will do that

[David Richards]

Hi - just for information.

JMX metrics started reporting as expected with JBOSS EAP 6.4 and JRE 1.8.

With JRE 1.7 we were still not getting the expected metrics back.

[Haruhiko Davis]

dave.richards

Which JRE 7 update are you testing on?

[David Richards]

This is the filter we use -

 

     introscope.agent.jmx.name.filter=jboss.as|data-source*,jboss.as|deployment*

 

JBOSS version we use -

 

     Red Hat JBoss Enterprise Application Platform - Version 6.4.0.GA

 

Does not work with this JRE

 

     java version "1.7.0_79"

     Java(TM) SE Runtime Environment (build 1.7.0_79-b15)

     Java HotSpot(TM) 64-Bit Server VM (build 24.79-b02, mixed mode)

 

Does work with this JRE

 

JBoss Enterprise Application Platform - Version 6.4.0.GA

 

     /usr/java/jdk1.8.0_66/bin/java -version

     java version "1.8.0_66"

     Java(TM) SE Runtime Environment (build 1.8.0_66-b17)

     Java HotSpot(TM) 64-Bit Server VM (build 25.66-b17, mixed mode)

 

 

Snapshot of working output shown below

 

[Haruhiko Davis]

Have you tried using JRE 7 Update 80?

[David Richards]

I have not, our runtime environments are installed by a different team so we use what is there as part of their standard build, as that is where the APM agent will have to run in production.

.

They do get patched though, are you aware of a fix or some other reason why it may start to work with update 80 ?

[Haruhiko Davis]

I'm not aware of any off the top of my head; it was really just a though that maybe it was due to that update. You may want to look at the release notes for your agent version to look for known issues.

[David Richards]

OK thank you anyway. We have a workable solution with JRE 1.8 as that is part of our standard builds now.