AQXPL5009E Another test case result is already named
Hello,
I want to integrate my testtool with RQM 5.0.1 using a custom automation adapter (OSLC) based on https://git.eclipse.org/r/#/admin/projects/lyo/org.eclipse.lyo.client Right now I got an 500 status code returned by the server when I try to save the test case result. Since the adapter runs on other servers seamlessly I assume it is a server configuration issue. I got some insight in the qm.log: 2015-02-26 07:28:42,931 [WebContainer : 31 @@ 07:28 DYG9SI /qm/oslc_auto_test/contexts/_5RnTU-dJEeKzfc0TjbXmmg/resources/com.ibm.rqm.execution.ExecutionResult] ERROR com.ibm.rqm.planning.service - TestArtifactCommon:getUniquessNameContraintErrorMessage AQXPL5009E Another test case result is already named "<...>" 2015-02-26 07:28:42,947 [WebContainer : 31 @@ 07:28 DYG9SI /qm/oslc_auto_test/contexts/_5RnTU-dJEeKzfc0TjbXmmg/resources/com.ibm.rqm.execution.ExecutionResult] ERROR com.ibm.rqm.oslc.service - AbstractOslcService:handleOslcRequest AQXCM5011E A server error occurred while running the HTTP operation, POST, at this URL: https://<...>/qm/oslc_auto_test/contexts/_5RnTU-dJEeKzfc0TjbXmmg/resources/com.ibm.rqm.execution.ExecutionResult. The response code is 500. com.ibm.team.repository.common.TeamRepositoryException: AQXPL5009E Another test case result is already named "<...>" at com.ibm.rqm.planning.service.internal.TestArtifactCommon.getUniquessNameContraintErrorMessage(TestArtifactCommon.java:1894) at com.ibm.rqm.planning.service.internal.TestArtifactCommon.nameUniquenessConstraint(TestArtifactCommon.java:1804) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:611) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56) at com.sun.proxy.$Proxy2726.nameUniquenessConstraint(Unknown Source) at com.ibm.rqm.execution.service.internal.rest.ExecutionResultRestService.postExecutionResult(ExecutionResultRestService.java:458) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) At first glance I couldn't find a setting, precondition or whatsoever which defines that every test case result has to be named uniquely. Is the title meant to unique or is the "name" something different? Google and forum-search right here couldn't give me an answer. Thanks in advance Michael |
Accepted answer
Hi Michael,
This is because of the uniqueness constraint we have for the artifact name. Did you try creating a Testcase Result with a different name which doesnt exist in the server? Michael Frembs selected this answer as the correct answer
Comments
Michael Frembs
commented Mar 12 '15, 3:56 a.m.
Hi Reshma,
|
One other answer
The issue has been also identified as RQM defect: https://jazz.net/jazz02/web/projects/Rational%20Quality%20Manager#action=com.ibm.team.workitem.viewWorkItem&id=135239 There is APAR PI39122 created for that.
|
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.