Hi,

 

I’m having problems trying to get RHQ discover a Hibernate Statistics mbean deployed inside an application over a Jboss 4.2.3 server. Also, it happens the same when the app is inside a Tomcat container.

All jmx access/level flags (unauthenticated access, no ssl, port established) are in place in the JVM invocation , etc.

 

##  run.conf for the Jboss instance

JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote"

JAVA_OPTS="$JAVA_OPTS -Djavax.management.builder.initial=org.jboss.system.server.jmx.MBeanServerBuilderImpl"

JAVA_OPTS="$JAVA_OPTS -Djboss.platform.mbeanserver"

JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote.port=9003"

JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote.ssl=false"

JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote.authenticate=false"

.

.

Tried some methods from http://www.rhq-project.org/display/RHQ/Plugins+-+Demos+-+Monitoring+Hibernate to no avail (manually adding a service of type JMX Server)

 

I’m and dev team are kinda puzzled by this. The app uses Spring and Hibernate 3.1. A printscreen from Jconsole (below), or querying explicitly the mbean via RMI ..works ok.Tried also using excellent jmx_console app from Phillip Traeder,  and works ok too:

 

root@fuchinos:/opt/jmxtools# ./jmx_console.sh get_attribute  --host=j2ee --port=9003 --object_name=org.hibernate:type=statistics --attribute_name=Queries

org.hibernate:type=statistics/Queries : select p from ParametroConfiguracion p

root@fuchinos:/opt/jmxtools#

 

I’m not a java developer, but I’m guessing there would be some sort of deviation in the manner the dev team initialized the Hibernate JMX mbean, perhaps the naming is not being recognized by the Hibernate RHQ plugin because of that?

 

Any help is much appreciated. Sorry the length and the print screens below, they are meant to illustrate a work ok/no ok view (the Hibernate plugin folder missing from “j2ee” Jboss instance).

 

N.b.: print screens erased, since they exceed the maximum for the list.

 

Regards,

 

Alvaro