Which version of hibernate do you use?
Can you post a more complete stack-trace of the
ArrayIndexOutOfBoundsException?
Do you use your datasource via Spring and by defining it in the spring
xml context perhaps? If yes, have you tried to monitor this datasource
in Spring and not with javamelody's HibernateBatcherFactory?
See http://code.google.com/p/javamelody/wiki/UserGuide?tm=6#7._JDBC
(Note that SpringDataSourceFactoryBean was added in javamelody 1.27 and
is not available in javamelody 1.26)
Thanks,
Emeric
Le 28/04/2011 13:51, Bart a �crit :
Are you sure that you used the same period in firefox and in IE?
It is a fact that the period is stored in a cookie on the client and is
persisted across browser restarts.
So it may explain that you used different periods depending on the
browser and so the NaN values in the graphics.
To sum up, if you have NaN values in the graphics:
- check the period displayed (the day period has values before the year
period)
- be sure that your server is used enough on a regular basis
- wait one day to have more values
bye, Emeric
Le 03/05/2011 15:47, Bart a �crit :
> For info: the empty graphs and NaN values are due to my browser,
> firefox 3.6.16. It works fine in IE.
>
> Bart
>
> On May 2, 11:59 pm, Emeric Vernat<ever...@free.fr> wrote:
>> Hi,
>>
>> It was a silly mistake in HibernateBatcherFactory. And I have changed
>> the code to reverse the "if" and it should work now.
>> It is committed in trunk and it is ready for the next release (1.29).
>> I have made a new build from the current trunk including the fix and, if
>> you want to try it, it is available at:http://javamelody.googlecode.com/files/javamelody-20110502.jar
>>
>> Please let us know if you verify the fix with this build or with the
>> next release.
>>
>> @Bart:
>> By the way, for the log below saying "rebinding datasources failed, skipping
>> ClassNotFoundException: org.apache.naming.ContextAccessController", it
>> is just a log and it does not stop the monitoring.
>> The cause of that log seems to be that in your JBoss 4.0.5, the server
>> does not name itself "JBoss" (but probably "Tomcat") as you can also
>> read yourself on the "Server" line in the "System informations" part of
>> the report. And so javamelody tries to monitor your datasource as in
>> Tomcat, and failing to that, javamelody just skips the monitoring of
>> your datasource.
>>
>> Thanks,
>> Emeric
>>
>> Le 02/05/2011 22:58, Philip Zeyliger a �crit :