Error: CRRTC4603E: There seems to be a circularity in the web dependencies of record type ChangeRequest

Technote (troubleshooting)


Problem(Abstract)

Unable to sync records from IBM Rational ClearQuest (CQ) to IBM Rational Team Concert (RTC) or Rational Quality Manager (RQM) using ClearQuest connector. Reporting error: CRRTC4603E: There seems to be a circularity in the web dependencies of record type ChangeRequest

Symptom

You are receiving the errors similar to the following:

Outgoing at 3/30/11 7:32:36 PM EDT

Error occurred:

java.lang.RuntimeException: com.ibm.team.interop.service.managers.clearquest.common.InteropException: CRRTC4603E: There seems to be a circularity in the web dependencies of record type ChangeRequest.

[( Classification -> Categorization ), ( Classification -> PriorityAuthorization ), ( Project -> Classification ), ( Project -> PrimarySubProject ), ( Project -> PriorityAuthorization ), ( Project -> SubProjects ), ( PrimarySubProject -> SubProjects ), ( Priority -> PriorityAuthorization ), ( PriorityAuthorization -> Priority ), ( PriorityAuthorization -> Project )]

Either fix them in the CQ designer or explicitly specify the field dependencies using the property cq.orderedProperties.<record type name>

com.ibm.team.interop.service.managers.clearquest.common.InteropException: CRRTC4603E: There seems to be a circularity in the web dependencies of record type ChangeRequest.

[( Classification -> Categorization ), ( Classification -> PriorityAuthorization ), ( Project -> Classification ), ( Project -> PrimarySubProject ), ( Project -> PriorityAuthorization ), ( Project -> SubProjects ), ( PrimarySubProject -> SubProjects ), ( Priority -> PriorityAuthorization ), ( PriorityAuthorization -> Priority ), ( PriorityAuthorization -> Project )]

Either fix them in the CQ designer or explicitly specify the field dependencies using the property cq.orderedProperties.<record type name>

Cause

The CQ Connector does handle fields with web dependencies, but according to the error message, there is a circular dependency in the ordering of the fields within the ChangeRequest record type.

[( Classification -> Categorization ), ( Classification -> PriorityAuthorization ), ( Project -> Classification ), ( Project -> PrimarySubProject ), ( Project -> PriorityAuthorization ), ( Project -> SubProjects ), ( PrimarySubProject -> SubProjects ), ( Priority -> PriorityAuthorization ), ( PriorityAuthorization -> Priority ), ( PriorityAuthorization -> Project )]

Resolving the problem

The way to look at the above information is the field before the arrow is dependent on the field after the arrow.

( Project -> PriorityAuthorization ), ( Priority -> PriorityAuthorization ), ( PriorityAuthorization -> Priority ), ( PriorityAuthorization -> Project )]

With that being said, the dependencies above have the circular dependency problem. It says Project field is dependent on the PriorityAuthorization field and at the same time the PriorityAuthorization field is dependent on the Project field. The same problem is there for the Priority and PriorityAuthorization field.

Other than fixing the circular dependency in CQ designer, you can specify the ordering of the fields in the cqconnector.properties file using the cq.orderedProperties.<record type name> whose value would contain a comma separated list of ordered properties.

Example: cq.orderedProperties.ChangeRequest=Project,PriorityAuthorization

Leverage the Jazz Community

Jazz and Rational Team Concert have an active community that can provide you with additional resources. Browse and contribute to the User forums, contribute to the Team Blog and review the Team wiki.
Refer to technote 1319600 for details and links.

Rate this page:

(0 users)Average rating

Document information


More support for:

Rational Team Concert
Integrations: IBM

Software version:

2.0, 2.0.0.1, 2.0.0.2, 3.0

Operating system(s):

AIX, Linux, Solaris, Windows

Reference #:

1499760

Modified date:

2012-07-16

Translate my page

Machine Translation

Content navigation