Steps to reproduce:
1. Set a job to CANCELLED (status = 9)
2. Go to the statistics page
All service stats are now zero
The correct service stats
Workaround (if any):
Don't cancel any jobs
We had this exact issue with our staging and production systems. So we applied this patch to our production server (1.5) and though it had worked on the staging server it failed causing the service registry to fail.
I think you fix is correct but has revealed a further issue with the way this function handles possible data combinations. As I sad it worked fine on our staging environment but failed on the production which obviously has a much larger database of jobs.
Maybe I should open a new ticket but I hope to delve a little deeper to see what could be causing the null pointer.
Also why is the serviceRegistry dependant on the JMX statistics bean working correctly?
This is merged already, so I close it