Quartz errors break down the frontend about javamelody HOT 1 CLOSED

I understand the problem.
It seems a bit strange to me to keep in the database jobs with classes which 
don't exist any more, but the report should be displayed anyway.
Those invalid jobs can't be displayed with an error status, so the invalid jobs 
will be ignored to fix the issue and they will not be displayed in the report 
(the exception above will be logged at "debug" level for each of those jobs).

I have committed the fix in trunk (revision 1304) for the next release (1.21).
I have made a new build, from the current trunk including the fix, which is 
available at:
http://javamelody.googlecode.com/files/javamelody-20101006.jar