CC sync reporting sync stream in use by other process
Hi
Thanks to earlier help on this forum I managed to get the CC sync working but this has just stopped working with the CC sync reporting that the synchronised stream is being used by another process. How can I find this out and what would the correction activity be? 2008-05-13 14:50:27 Should build occur? 2008-05-13 14:50:27 Yes: Always build a user initiated request. 2008-05-13 14:50:28 Invoking build participant "com.ibm.team.build.ant" Buildfile: C:\TeamConcert-1.0M6a-win32\jazz\buildsystem\buildtoolkit\ScmConnectors\synchronizeStream.xml readProperties: read ccsync.properties checkEnv: Sync: action: synchronize synchronization stream location string: Stream|URI:itemOid/com.ibm.team.scm.Workspace/_7hT30B3EEd2HOen15rOWBg Synchronization exception: Synchronized stream in use by other process BUILD FAILED C:\TeamConcert-1.0M6a-win32\jazz\buildsystem\buildtoolkit\ScmConnectors\synchronizeStream.xml:66: javax.wvcm.WvcmException: Synchronization failed. Total time: 8 seconds Build failed. Exit value was 1. javax.wvcm.WvcmException: Synchronized stream in use by other process at com.ibm.rational.wvcm.interop.InteropStream.lockInteropStream(InteropStream.java:373) at com.ibm.rational.wvcm.interop.InteropStream.reserveInteropStream(InteropStream.java:408) at com.ibm.rational.wvcm.interop.InteropStream.sync(InteropStream.java:3094) at com.ibm.team.connector.scm.operations.ConnectorOps.synchronizeStream(ConnectorOps.java:144) at com.ibm.team.connector.scm.task.ConnectorTasks.updateBuildResult(ConnectorTasks.java:91) at com.ibm.team.build.ant.task.AbstractPublisherTask.doExecute(AbstractPublisherTask.java:107) at com.ibm.team.build.ant.task.AbstractTeamBuildTask.execute(AbstractTeamBuildTask.java:407) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:357) at org.apache.tools.ant.Target.performTasks(Target.java:385) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329) at org.apache.tools.ant.Project.executeTarget(Project.java:1298) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) at org.apache.tools.ant.Project.executeTargets(Project.java:1181) at org.apache.tools.ant.Main.runBuild(Main.java:698) at org.apache.tools.ant.Main.startAnt(Main.java:199) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104) |
2 answers
Geoffrey Clemm (30.1k●3●30●35)
| answered May 13 '08, 11:00 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Usually, this just means that the sync is taking longer than expected
.... look at the processes running on your synchronization host ... if there are cleartool's running, then the sync is still running. If the sync-engine process dies because of some hard crash (hardware crash, internal software error), the sync-stream metadata can be left locked . Once you've convinced yourself that this is the problem, you would go to the ClearCase tab on the synchronized stream Properties page, and select the "unlock" button. Then just request another sync, and one should fire up. Cheers, Geoff marko wrote: Hi |
Thanks Geoff, worked a treat. Much appreciated.
|
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.