Synchronisation Errors between RRC and ReqPro - please help
Hi,
Last year I had version 1.0 of RRC syncing perfectly with ReqPro (7.1 I believe) - 2 way sync working without a problem. We then moved away from ReqPro for a while as we became engaged in a lot of prototype based agile projects and used RRC (V2.0) exclusively. We have recently started 2 more traditional waterfall style projects and have returned to ReqPro (7.1.1.1) for Requirements Management. I have had nothing but headaches trying to get the syncing working this time. I am receiving a number of errors in rdm.log - some referencing user authentication timeouts and potential incorrect address errors (which I think are a symptom of something else)......every couple of attempts I receive this error: "2010-06-25 11:31:39,175 ERROR er.services.servicedocument.ProjectResourceService - HTTP/1.1 409 CRJZS5054E If-Match () was not equal to the resource ETag ("_b4IvAYA8Ed-1yopHludBZA") and was not a wildcard. com.ibm.rdm.fronting.server.exception.UnexpectedResponseException: HTTP/1.1 409 CRJZS5054E If-Match () was not equal to the resource ETag ("_b4IvAYA8Ed-1yopHludBZA") and was not a wildcard. at com.ibm.rdm.fronting.server.core.internal.InternalDomainServiceBase.doPutInternal(InternalDomainServiceBase.java:307) at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.runInternalMethod(RRSRestServiceBase.java:219) at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.handleMethod(RRSRestServiceBase.java:171) at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.doPut(RRSRestServiceBase.java:80) at com.ibm.team.jfs.app.servlet.AppContainerServlet.dispatchRequest(AppContainerServlet.java:109) at com.ibm.team.jfs.app.servlet.AppContainerServlet.service(AppContainerServlet.java:181) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90) at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111) at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:75) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:121) at com.ibm.team.repository.server.servletbridge.JazzServlet.service(JazzServlet.java:54) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:870) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685) at java.lang.Thread.run(Thread.java:811) 2010-06-25 11:31:39,175 ERROR er.services.servicedocument.ProjectResourceService - Response: 409 CRJZS5054E If-Match () was not equal to the resource ETag ("_b4IvAYA8Ed-1yopHludBZA") and was not a wildcard. - for request: PUT https://e<myserver>:9443/rdm/project-resources/_Z4bhEIA8Ed-1yopHludBZA HTTP/1.1 2010-06-25 11:31:39,175 ERROR er.services.servicedocument.ProjectResourceService - Response: 409 CRJZS5054E If-Match () was not equal to the resource ETag ("_b4IvAYA8Ed-1yopHludBZA") and was not a wildcard. - for request: PUT https://<myserver>:9443/rdm/project-resources/_Z4bhEIA8Ed-1yopHludBZA HTTP/1.1" Could somebody please explain what is going on here? I know that synchronisation was brought down for V2.0, but had understood that it returned from version 2.0.0.1....has anyone successfully managed to get 2 way syncing working? Has anyone else encountered the above error and managed to figure it out? Any help at all would be much appreciated...... My levels are as follows: RRC (Client and Server): 2.0.0.2 ReqPro: 7.1.1.1 connected to DB2 9.1.401.444 (with the integration update patch installed) Both user repositories are authenticated via LDAP realms. Thanks, Peter.... |
One answer
Hi, Configuring for the integration: Rational Requirements Composer Server and Client both running at 2.0.0.1 Rational RequisitePro ReqWEB component installed 7.1.1 iFix01 New DB Schema Requires an enterprise database (SQL Server, Oracle, DB2) Run TLogSchemaUpdate.sql script in order to update the schema Also: The ReqPro user used in establishing the connection to ReqPro should not be the user used for making changes in ReqPro. This users changes will not be picked up by the sync if it is used in ReqPro. There is a topic in help as a preliminary setup step to create this user. Uploads from archives retain the links that were saved to the archive. This is a problem since the connection to the requirement is no longer valid and the user does not have a way to remove the links in this version of Composer. Warnings in RRC client for upgrade users. You cannot invoke Edit Connection, Manage Requirement, Import Requirement, and Synchronize Attribute Groups without update the ReqPro DB schema. Access not supported for the connected ReqPro project. A setting was added in the 2.0 fronting.properties that disabled the sync for the whole repository. The setting should have been removed in 2.0.0.1. Make sure this value is not present for the sync to work: com.ibm.rdm.fronting.server.synchronizing=false Attributes and list items are never deleted by the sync. If you remove an attribute or a list item from one side and sync, the corresponding item will not be removed from the other side. I hope this helps. |
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.