AnsweredAssumed Answered

Connecting to JMX MBeans - possible bug

Question asked by michalwrobel on Feb 2, 2012
Latest reply on Feb 2, 2012 by michalwrobel
I'm using Alfresco 4.0c

I succesfully connected to JMX in remote (virtual box machine) Alfresco instance with Jconsole but it doesn't show what it should.
I see only "VirtServerRegistry" MBean

As author of this article
http://www.ixxus.com/blog/2011/02/monitor-and-manage-alfresco-via-jmx/
says

Note. If you only see one MBean under the Alfresco namespace then you might have a version of Alfresco where there is currently a bug so you will only see the VirtServerRegistry entry. This was the case with version 3.4c, I had to switch to 3.3.4 for it to work

Alfresco has been afflicted with this kind of problem since much older releases..

So, is this really so long lasting a bug?

I used followingJVM options to configure JMX:

-Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.port=6060
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=false
-Djava.rmi.server.hostname=10.8.0.90 # I had to specify this explicitly because JMX wasn't 'mapped outside' correctly without this setting (like in this post http://stackoverflow.com/questions/1263991/connecting-remote-tomcat-jmx-instance-using-jconsole)

Outcomes