Setting jobs to CANCELLED breaks the statistics display

Steps to reproduce

Steps to reproduce:
1. Set a job to CANCELLED (status = 9)
2. Go to the statistics page

Actual Results:
All service stats are now zero

Expected Results:
The correct service stats

Workaround (if any):
Don't cancel any jobs


James Perrin
January 26, 2015, 2:08 PM

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.

Greg Logan
January 26, 2015, 5:09 PM

I don't see how this fix could have caused that, considering it's one line in the javascript ( What exactly is nulling out? Is your prod 1.5 server identical in codebase to the upstream code?

James Perrin
January 28, 2015, 10:51 AM

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?

Rüdiger Rolf
February 18, 2015, 10:47 AM

This is merged already, so I close it


Rüdiger Rolf


Greg Logan


Incorrectly Functioning Without Workaround

Tags (folksonomy)


Fix versions

Affects versions