Unable to restart synchronization engine...
Hi,
I have set up synchronization between ClearCase and RTC successfully. I managed also to exchange once the contents from one to the other with no problems. My synchronization host is a Linux RedHat RHEL 5 system with RTC 1.0 RC4 and ClearCase 7.0.1. I verified that everything works fine for ClearCase, as we use it as our source control system already. In one synchronization, there was a timeout due to network problems, so the synchronization stalled for 48 hours. After that time, I decided to stop the ClearCaseConnector process. I used kill -9 to remove the synchronization engine, as I couldn't find any option to do it from RTC. Now, the problem is that RTC is reporting this error every time I want to restart the synchronization engine:
There is also this exception in the "Synchronization Stack Trace.0" file:
I couldn't find any process that might be using this synchronized stream, and even restarted the synchronization host to start with a clean environment. Any pointers would be helpful. Thanks, Karim |
2 answers
Geoffrey Clemm (30.1k●3●30●35)
| answered Jul 22 '08, 7:01 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Please see the dynamic help topic: "Unlocking a synchronized stream".
In particular, it says: --------- If the synchronization engine process is terminated or the Jazz Team Server becomes unreachable during a synchronization, the synchronized stream remains locked. You must unlock the stream and then re-start the synchronization process. To unlock a synchronized stream: Open the ClearCase Synchronized Streams view, right-click the stream that is locked and click Properties. On the ClearCase Provider Properties page, click Unlock. Re-start the synchronization process. For more information, see Re-starting the synchronization process. --------- Cheers, Geoff karim.heredia wrote: Hi, |
|
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.