RTC 5.0.2, Windows 7. Also occurred in previous versions of RTC.
We are occasionally getting RTC command line scm errors from our overnight processing. This occurs about one in every four overnight project builds. The command that gets the error is:
call "C:\Program Files\IBM\TeamConcert\scmtools\eclipse\scm" --non-interactive login -r https://server:9453/ccm -n RTC_AFM -u user-P password -c
And the error message (about 10 minutes later) is:
Unexpected exception
com.ibm.team.rtc.cli.infrastructure.internal.core.CLIClientException: Waited for 40000ms, but FSDaemon failed to come up
at com.ibm.team.filesystem.cli.core.util.StatusHelper.toCLIClientException(StatusHelper.java:731)
at com.ibm.team.filesystem.cli.core.AbstractSubcommand.run(AbstractSubcommand.java:53)
at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.run(SubcommandLauncher.java:601)
at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.doStart(SubcommandLauncher.java:370)
at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.run(SubcommandLauncher.java:130)
at com.ibm.team.rtc.cli.infrastructure.internal.Application.start(Application.java:41)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:94)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
at java.lang.reflect.Method.invoke(Method.java:619)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
at org.eclipse.equinox.launcher.Main.run(Main.java:1408)
at org.eclipse.equinox.launcher.Main.main(Main.java:1384)
Caused by: java.lang.IllegalStateException: Waited for 40000ms, but FSDaemon failed to come up
at com.ibm.team.filesystem.client.restproxy.Discovery2.startInProcess(Discovery2.java:931)
at com.ibm.team.filesystem.client.restproxy.Discovery2.createDaemon(Discovery2.java:842)
at com.ibm.team.filesystem.client.restproxy.Discovery2.resolve(Discovery2.java:723)
at com.ibm.team.filesystem.cli.core.util.SubcommandUtil.startDaemon(SubcommandUtil.java:981)
at com.ibm.team.filesystem.cli.core.util.SubcommandUtil.startDaemon(SubcommandUtil.java:917)
at com.ibm.team.filesystem.cli.core.util.SubcommandUtil.setupDaemon(SubcommandUtil.java:1290)
at com.ibm.team.filesystem.cli.client.internal.subcommands.LoginCmd.run(LoginCmd.java:78)
at com.ibm.team.filesystem.cli.core.AbstractSubcommand.run(AbstractSubcommand.java:51)
... 17 more
Does anyone know how to fix it?
Thanks in advance,
Eddie