It looks like that the classpath of "jconsole" may not contain a proper version of the "hibernate3.jar" or "hibernate-core-.jar". When this happens, the monitoring plugin wont be able to read the JMX exports from hibernate. This is caused by the fact that hibernate uses proprietary serializable data structures without any serial-version-uid to transmit any statistical details.
Simple attributes, like the data that is shown in the primary graph can be read as this information is transmitted via standard data-types as defined by the JMX standard.
The current version of the plugin does contain some checks regarding the classpath however it still may be that it is run with an incorrect version. Try starting the JAR via:
Currently I'm working on a version that is more intelligent in detecting the remote version of hibernate and contains integration with the Maven repo. From the next release on it should be much easier to overcome this obstacle.
Nevertheless I hope that the recommendation from above will do the trick.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The CI tests that I have show that queries and entities tabs work fine with hibernate 4 (at least with 4.0.0 and 4.1.7 which are the tested versions).
If the classpath isn't the issues in your case then there's also another point that could lead you to the same result: If you do not execute any JQL/HQL queries then you won't see any queries in the queries tab as it shows only those statements that you created using "entityManager.createQuery(..)".
If this is also not the problem you potentially spotted a bug. Does JConsole output any stack traces that you could post?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, i have a problem. the queries view show me graph but none query. Where i wrong? Thanks!
Hi,
It looks like that the classpath of "jconsole" may not contain a proper version of the "hibernate3.jar" or "hibernate-core-.jar". When this happens, the monitoring plugin wont be able to read the JMX exports from hibernate. This is caused by the fact that hibernate uses proprietary serializable data structures without any serial-version-uid to transmit any statistical details.
Simple attributes, like the data that is shown in the primary graph can be read as this information is transmitted via standard data-types as defined by the JMX standard.
The current version of the plugin does contain some checks regarding the classpath however it still may be that it is run with an incorrect version. Try starting the JAR via:
Currently I'm working on a version that is more intelligent in detecting the remote version of hibernate and contains integration with the Maven repo. From the next release on it should be much easier to overcome this obstacle.
Nevertheless I hope that the recommendation from above will do the trick.
Would this be the reason I cant get the plugin to work with hibernate 4?
The CI tests that I have show that queries and entities tabs work fine with hibernate 4 (at least with 4.0.0 and 4.1.7 which are the tested versions).
If the classpath isn't the issues in your case then there's also another point that could lead you to the same result: If you do not execute any JQL/HQL queries then you won't see any queries in the queries tab as it shows only those statements that you created using "entityManager.createQuery(..)".
If this is also not the problem you potentially spotted a bug. Does JConsole output any stack traces that you could post?