Bug #4959
closedReporting call to getDefaultProvenaceRecorder occasionally gets an NPE
0%
Description
Sometimes when you execute a workflow in WRP, you'll get an NPE from Reporting when it calls ProvenaceRecorder.getDefaultProvenaceRecorder. I think this may be related to changing the report and rerunning the workflow but I'm not sure...
Updated by Derik Barseghian almost 14 years ago
Now I think this happens when you make a change to certain workflows and an entirely new lsid is gotten, and the old one is placed in the derived from list, instead of just bumping the revision. I'm not sure of all the cases in which this occurs (it seems like this sometimes happens when it shouldn't, but that would be a separate issue), but one is when you rename the workflow. When a new lsid is assigned to the workflow, the call to get the workflow out of ObjectManager in getProveanceRecorder returns null, even though the new lsid is used:
NamedObj reference = ObjectManager.getInstance().getHighestObjectRevision(lsid);
Updated by Derik Barseghian almost 14 years ago
Re: new lsid added and referral generated when it shouldn't, I think I was wrong, this is happening when a new namespace is in use, as it should.