Hey Yergali, Suggestion: step-1: enable setting to true to see if any other JMX mbeans are not getting stopped due to flag https://docs.appdynamics.com/appd/22.x/latest/en/application-monitoring/install-app-ser[…]-installation-by-java-framework/glassfish-startup-settings step-2: Post above setting, in recent versions the approach is below: a) Agent creates JMX metrics as per mbeans exposed by JVM which could be seen in node dashboard -> JMX -> MBean browser (this is like JConsole), so the suggestion to user is to check first if target JDBC conncection mbean are exposed by JVM under “Mbean browser” in target sub category in list we see in controller UI b) If we see target mbean browser than the suggestion is to use “create metric” step as in doc link by selecting target attribute and then add any more more attributes so that JMX rule will be created.c) Post step-b above agent will try to match new JMX rule mbean and attributes with JVM exposed mbean object pattern (like mbean browser) and it will report in “metric browser” at tier/node -> JMX section (edited)  If this does not work out, I recommend filing a support ticket and tag here. We can take it up  Hope this helps Regards, Abhinav ... View more

Hey @Maria.Garcia, @Sunil.Chatooa, @Nitin.Walunj  I am the product manager for the Java agent. Was this issue ever addressed? Can you share the support key for reference ? If not resolved yet, I will actively get it addressed Thanks, Abhinav ... View more

Hey Nandani, Can you file a support ticket and share in this channel. I will ensure it gets verified and resolved soon. ... View more