EAP6 plugin does rely on JMX but on the EAP HTTP Management Interface. Some of the MBeans are accessible under the "JVM" resource, but not custom MBeans. This is why you can't see your MBeans under your server resource.
Besides, EAP 6 does not declare com.sun.management.jmxremote system properties by default. This is why the JMX plugin cannot discover the EAP6 JVM.
Add com.sun.management.jmxremote properties to your standalone.conf file, restart your EAP server then trigger a detailed discovery (there is an operation on the platform resource for that).
Can you attach you standalone.conf.bat file?
Sorry wrong indication, you have hit [#AS7-1859] AS won't boot with sun jmx enabled - JBoss Issue Tracker
You can still manually import the JMX resource:
- In the "Inventory > Child Resources" tab of your platform resource, click on "Import > JMX Server".
- Select default template on the first step of the wizard
- In the second step of the wizard, fill the following properties:
Type: JSR 160
Connector Address: service:jmx:remoting-jmx://<SERVER IP>:9999
Install URI: <JBOSS_HOME>
Additional Class Path Entries: <JBOSS_HOME>/bin/client/jboss-client.jar
Thanks Thomas, It works perfectly. I can see the the metrics and execute operations.
As I mentioned before, I am using a ServletContextListener implementation to register the custom Mbeans. Is this the right approach? or Is there any best practice to follow?
I have more than 10 web-apps(.war) files in the production environment and I am plning to use custom MBeans to monitor each web-apps specific behaviours.
Any suggestions or guidence would be greatly appriciated.