AQXCM5001E occurs periodically in after RQM upgrade integrated with CCM
After upgrading to CLM 6.0, this error occurs periodically in qm.log every few minutes:
2015-08-18 00:07:00,542 [qm: AsynchronousTaskRunner-2 @@ 00:07] ERROR com.ibm.rqm.defects.service - ChangeRequestCollector:runTask AQXCM5001E The OSLC request to connect to a remote server failed. Project area: Sandbox (Quality Management); Connection URL: https://<HOST>:9443/ccm/oslc/contexts/.../workitems/services.xml; Details: null.
What causes this and how can it be resolved?
2015-08-18 00:07:00,542 [qm: AsynchronousTaskRunner-2 @@ 00:07] ERROR com.ibm.rqm.defects.service - ChangeRequestCollector:runTask AQXCM5001E The OSLC request to connect to a remote server failed. Project area: Sandbox (Quality Management); Connection URL: https://<HOST>:9443/ccm/oslc/contexts/.../workitems/services.xml; Details: null.
What causes this and how can it be resolved?
One answer
This happens every few minutes as each project area is trying to connect
from QM to CCM to syncronize linked work items.
The problem occurs because the upgrade guide was missing a step which we
have since added in higher versions:
This is the second yellow box on this page:
https://www-01.ibm.com/support/knowledgecenter/SSYMRC_6.0.1/com.ibm.rational.test.qm.doc/topics/t_config_rtc_defects_overview.html?lang=en.
So add the user qm_user as the "functional user" for the consumer
entry qm/rootservices on your CCM server administration page. This was
mentioned as an "optional" step in the instructions for establishing
cross-server communication (step 10.e), but is really mandatory for your
scenario.
The expected impact is that if you have links between QM and CCM work
items, the true status of work items may not be reflected in QM.
from QM to CCM to syncronize linked work items.
The problem occurs because the upgrade guide was missing a step which we
have since added in higher versions:
This is the second yellow box on this page:
https://www-01.ibm.com/support/knowledgecenter/SSYMRC_6.0.1/com.ibm.rational.test.qm.doc/topics/t_config_rtc_defects_overview.html?lang=en.
So add the user qm_user as the "functional user" for the consumer
entry qm/rootservices on your CCM server administration page. This was
mentioned as an "optional" step in the instructions for establishing
cross-server communication (step 10.e), but is really mandatory for your
scenario.
The expected impact is that if you have links between QM and CCM work
items, the true status of work items may not be reflected in QM.
Comments
And if you are using the CCM/RQM build integration (CCM is the build provider) you must also ensure that qm_user has the "Rational Quality Manager - Connector" license for build definitions and records to sync correctly.
Hello,
Quick question on this answer. I understand after the upgrade to 6.x the need to fix the qm_user, but can this be applied to 5.0.2 without issues?
I don't remember seeing this in the interactive upgrade guide when we moved from 5.0.2 to 6.0.3 but we did see this problem and hoping that this changes it. Thanks Erik for putting up this question!