Do these log messages simply mean QM project has no configured Defect provider ?
Today I notice what I thought were new messages [ but they aren't, records in 2013 show ] in the QM application logs
CRJAZ1451E The DefectTrackingTask task from the com.ibm.rqm.execution component could not be completed and will be rescheduled.
java.lang.NullPointerException
at com.ibm.rqm.execution.service.internal.DefectTrackingService.synchronizeDefectState(DefectTrackingService.java:128)
[there is more, but omitted for brevity ]
I can say with certainty that there are QM projects that exist w/o Uses association for Defects.
Thanks
CRJAZ1451E The DefectTrackingTask task from the com.ibm.rqm.execution component could not be completed and will be rescheduled.
java.lang.NullPointerException
at com.ibm.rqm.execution.service.internal.DefectTrackingService.synchronizeDefectState(DefectTrackingService.java:128)
[there is more, but omitted for brevity ]
I can say with certainty that there are QM projects that exist w/o Uses association for Defects.
Thanks
Accepted answer
The DefectTrackingTask is used to unblock test case execution records automatically (see https://jazz.net/help-dev/clm/topic/com.ibm.rational.test.qm.doc/topics/t_config_auto_unblocking.html). The NullPointerException is a defect but may be fixed in RQM 6.0 under DefectTrackingTask/DefectTrackingService/QualityManagerConfigurationService need better exception handling (118402) and/or ItemNotFoundExection in DefectTrackingTask (122260). What version of RQM are you running?
