Error on 'scm load' - $Proxy14 ClassCastException

Dave Westerman (33●11●10) | asked May 05 '10, 10:01 a.m.

I was trying to do an 'scm load' using the command line from the RTC Eclipse client, and got the following error:


C&#58;\RTC\LynxDevStream&gt;\RSDP75\scmtools\eclipse\scm load -r https&#58;//rtp-rtc12.tivlab.raleigh.ibm.com&#58;9443/jazz/ 1014

Password &#40;dlwester@us.ibm.com @ https&#58;//rtp-rtc12.tivlab.raleigh.ibm.com&#58;9443/jazz/&#41;&#58;

Unexpected exception

java.lang.ClassCastException&#58; $Proxy14 incompatible with com.ibm.team.scm.common.IWorkspace

        at com.ibm.team.filesystem.cli.core.util.RepoUtil.findNamedWorkspace&#40;Unknown Source&#41;

        at com.ibm.team.filesystem.cli.client.internal.subcommands.LoadCmd.run&#40;LoadCmd.java&#58;126&#41;

        at com.ibm.team.filesystem.cli.client.internal.subcommands.LoadCmdLauncher.run&#40;LoadCmdLauncher.java&#58;161&#41;

        at com.ibm.team.filesystem.cli.core.internal.Application.run&#40;Unknown Source&#41;

        at com.ibm.team.filesystem.cli.core.internal.Application.doStart&#40;Unknown Source&#41;

        at com.ibm.team.filesystem.cli.core.internal.Application.start&#40;Unknown Source&#41;

        at org.eclipse.equinox.internal.app.EclipseAppHandle.run&#40;Unknown Source&#41;

        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication&#40;Unknown Source&#41;

        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start&#40;Un

known Source&#41;

        at org.eclipse.core.runtime.adaptor.EclipseStarter.run&#40;Unknown Source&#41;

        at org.eclipse.core.runtime.adaptor.EclipseStarter.run&#40;Unknown Source&#41;

        at sun.reflect.NativeMethodAccessorImpl.invoke0&#40;Native Method&#41;

        at sun.reflect.NativeMethodAccessorImpl.invoke&#40;NativeMethodAccessorImpl.java&#58;48&#41;

        at sun.reflect.DelegatingMethodAccessorImpl.invoke&#40;DelegatingMethodAccessorImpl.java&#58;37&#41;

        at java.lang.reflect.Method.invoke&#40;Method.java&#58;600&#41;

        at org.eclipse.equinox.launcher.Main.invokeFramework&#40;Unknown Source&#41;

        at org.eclipse.equinox.launcher.Main.basicRun&#40;Unknown Source&#41;

        at org.eclipse.equinox.launcher.Main.run&#40;Unknown Source&#41;

Scm&#58;

An error has occurred. See the log file

C&#58;\RTC\LynxDevStream\.metadata\.log.

Any ideas?

4 answers

Most liked answers ↑|Newest answers|Oldest answers

permanent link

Tim Mok (6.6k●3●8) | answered May 06 '10, 8:43 a.m.
JAZZ DEVELOPER

Did you check that the alias '1014' is an alias for a workspace? It's the first thing I can think of when looking at the source and it should have given you a better error message to help identify the problem.

I was trying to do an 'scm load' using the command line from the RTC Eclipse client, and got the following error:


C&#58;\RTC\LynxDevStream&gt;\RSDP75\scmtools\eclipse\scm load -r https&#58;//rtp-rtc12.tivlab.raleigh.ibm.com&#58;9443/jazz/ 1014

Password &#40;dlwester@us.ibm.com @ https&#58;//rtp-rtc12.tivlab.raleigh.ibm.com&#58;9443/jazz/&#41;&#58;

Unexpected exception

java.lang.ClassCastException&#58; $Proxy14 incompatible with com.ibm.team.scm.common.IWorkspace

        at com.ibm.team.filesystem.cli.core.util.RepoUtil.findNamedWorkspace&#40;Unknown Source&#41;

        at com.ibm.team.filesystem.cli.client.internal.subcommands.LoadCmd.run&#40;LoadCmd.java&#58;126&#41;

        at com.ibm.team.filesystem.cli.client.internal.subcommands.LoadCmdLauncher.run&#40;LoadCmdLauncher.java&#58;161&#41;

        at com.ibm.team.filesystem.cli.core.internal.Application.run&#40;Unknown Source&#41;

        at com.ibm.team.filesystem.cli.core.internal.Application.doStart&#40;Unknown Source&#41;

        at com.ibm.team.filesystem.cli.core.internal.Application.start&#40;Unknown Source&#41;

        at org.eclipse.equinox.internal.app.EclipseAppHandle.run&#40;Unknown Source&#41;

        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication&#40;Unknown Source&#41;

        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start&#40;Un

known Source&#41;

        at org.eclipse.core.runtime.adaptor.EclipseStarter.run&#40;Unknown Source&#41;

        at org.eclipse.core.runtime.adaptor.EclipseStarter.run&#40;Unknown Source&#41;

        at sun.reflect.NativeMethodAccessorImpl.invoke0&#40;Native Method&#41;

        at sun.reflect.NativeMethodAccessorImpl.invoke&#40;NativeMethodAccessorImpl.java&#58;48&#41;

        at sun.reflect.DelegatingMethodAccessorImpl.invoke&#40;DelegatingMethodAccessorImpl.java&#58;37&#41;

        at java.lang.reflect.Method.invoke&#40;Method.java&#58;600&#41;

        at org.eclipse.equinox.launcher.Main.invokeFramework&#40;Unknown Source&#41;

        at org.eclipse.equinox.launcher.Main.basicRun&#40;Unknown Source&#41;

        at org.eclipse.equinox.launcher.Main.run&#40;Unknown Source&#41;

Scm&#58;

An error has occurred. See the log file

C&#58;\RTC\LynxDevStream\.metadata\.log.

Any ideas?

permanent link

Dave Westerman (33●11●10) | answered May 06 '10, 11:15 a.m.

Thanks, Tim! That was it. I had been successfully loading the same workspace from a Linux machine, and made the erroneous assumption that the UUID used for the workspace would be the same from my Windows machine. That UUID is obviously not a global one.

permanent link

Tim Mok (6.6k●3●8) | answered May 06 '10, 11:30 a.m.
JAZZ DEVELOPER

Thanks, Tim! That was it. I had been successfully loading the same workspace from a Linux machine, and made the erroneous assumption that the UUID used for the workspace would be the same from my Windows machine. That UUID is obviously not a global one.

Ah yes, the '1014' alias that you saw is for the current session. It isn't a permanent alias for the item. If you rebooted your Linux machine, it might not be the same alias.

permanent link

Michael Valenta (3.7k●3) | answered May 07 '10, 9:35 a.m.
FORUM MODERATOR / JAZZ DEVELOPER

The UUID is a global id but the CLI surfaces aliases which are not.

Michael

dlwester wrote:

Thanks, Tim! That was it. I had been successfully loading the same
workspace from a Linux machine, and made the erroneous assumption
that the UUID used for the workspace would be the same from my
Windows machine. That UUID is obviously not a global one.

Your answer

Register or log in to post 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.

It's all about the answers!

Related questions

Error on 'scm load' - $Proxy14 ClassCastException

4 answers

Your answer