Error 409 and 500 while linking requirements to RQM testcases
Amit Garg (31●19●49)
| asked Nov 22 '13, 5:25 a.m.
edited Nov 24 '13, 12:55 p.m. by Lisa Caten (342●9●13) We have RQM 4.0.3 and DOORS 9.4. Linking to DOORS requirements works fine without any issues to other RQM project A but that is not the case with project B of RQM and specific module X in DOORS. Linking requirements from other modules to project B works fine. linking req from module X to project A does not work. We get the following two errors while saving the links: Unable to load /qm/proxy?uri=http%3A%2F%2Fclm%3A8080%2Fdwa%2Frm%2Furn%3Arational%3A%3A1-504dd9b9029f2803-M-00000080 status:409 AND Unable to load /qm/proxy?uri=http%3A%2F%2Fclm%3A8080%2Fdwa%2Frm%2Furn%3Arational%3A%3A1-504dd9b9029f2803-M-00000080 status:500 I understand that most of you would say that either its configuration problem or access rights is the problem. But I don't feel so because linking works fine without issues for one project so why it doesnt work for the other project. Secondly, for error 409 user has full access on the module and once the user again clicks on save "it works fine". Same is with error 500 at the moment. |
4 answers
Hey All,
I've got error No 409, but Doors was close.
The requirements collection link shows that there is a link between the requirement and the test case but the requirement link section in the test case and the links section in Doors (for the specific requirement) show nothing.
What happens and how can i fix it?
Thanks
Michal.
|
Hey Amit,
I have done some very brief testing and I got a 500 trying to link a test plan to a view (requirement collection) when the module is open in shared edit mode in DOORS; 500 when trying to link a test case to object when that object is locked in shared edit mode. No 409. But I think you should log a PMR.
Pragmatically, I would either create the links in DOORS or not use shared edit mode in DOORS during this process.
Maeve
|
|
Hi Maeve, The problem with 409 error is that when we click multiple times, the save works and if I check the locks on the module, there are 40-50 shareable locks are there as 4 users work on linking requirements to test cases. |
|
409 is usually a result of the module being open, in DOORS, in edit mode. So it's locked and RQM cannot write to it to create the backlink. Basically it must be able write to it - access or locks can impact that.
500 is harder. It could be DWA configuration, but I agree that would not explain it working elsewhere. As Paul says look in the logs. qm.log for RQM and server\festival\logs for DWA.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
Can you check the RQM and DOORS logs for related error messages?
2013-11-22 10:20:42,119 [WebContainer : 24 @@ 10:20 502221823 /qm/service/com.ibm.rqm.requirement.common.service.rest.ICalmRequirementRestService/updateCalmRequirementsModifiedTimes] ERROR com.ibm.rqm.requirement.service
CalmRequirementRestService:postUpdateCalmRequirementsModifiedTimes AQXRQ5002E Failed to update lastModifiedTime for Requirement URI: https://req-mgmt:443/dwa/rm/urn:rational::1-39c72c502c551fa5-O-785-0001c481, it failed because of: Can't find out the CalmRequirment by project areacom.ibm.team.process.internal.common.impl.ProjectAreaImpl@38dd38dd (stateId: [UUID _7kUkQFKKEeO1K6RjLa6WUQ], itemId: [UUID _9ZXil4vSEeKB0qnGvEIVYA], origin: <unset>, immutable: true) (contextId: [UUID _9ZXil4vSEeKB0qnGvEIVYA], modified: 2013-11-21 08:57:20.772, workingCopy: <unset> (mergePredecessor: null, workingCopyPredecessor: <unset>, workingCopyMergePredecessor: <unset>, predecessor: [UUID _955X0VEGEeO1K6RjLa6WUQ]) (descSummary: Sample Project V9 in DOORS, archived: false, name: Sample Project, uniqueName: Sample Project(JTS-Sentinel-Id)) (isInitialized: true, internalPublic: false, internalVisibleToMembers: true, internalVisibleToAccessList: false, owningApplicationKey: JTS-Sentinel-Id, internalIs