Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

Running "scm accept -o" in local Sandbox get error "java.lang.IllegalArgumentException: Invalid segment AFEHRMAZ\rcinit.md5"

I'm using the "scm accept" command line to update my local Sandbox during a product build. During the build, some repository files are modified in the Sandbox. So I use "scm accept -o" to load and overwrite the change sets to the Sandbox.
But some times the command failed with error:
*********************************************************************************
Unexpected exceptionjava.lang.IllegalArgumentException: Invalid segment AFEHRMAZ\rcinit.md5    at com.ibm.team.filesystem.client.internal.RelativeLocation.validateNameParts(RelativeLocation.java:79)    at com.ibm.team.filesystem.client.internal.RelativeLocation.append(RelativeLocation.java:89)    at com.ibm.team.filesystem.client.internal.LocalFileStorage.getChildren(LocalFileStorage.java:274)    at com.ibm.team.filesystem.client.internal.FileStorageWrapper.getChildren(FileStorageWrapper.java:652)    at com.ibm.team.filesystem.client.internal.Shareable.visit(Shareable.java:609)    at com.ibm.team.filesystem.client.internal.Shareable.access$0(Shareable.java:600)    at com.ibm.team.filesystem.client.internal.Shareable$1.visit(Shareable.java:260)    at com.ibm.team.filesystem.client.internal.core.SharingMetadata2.acceptAll(SharingMetadata2.java:1871)    at com.ibm.team.filesystem.client.internal.core.SharingMetadata2.acceptAll(SharingMetadata2.java:1883)    at com.ibm.team.filesystem.client.internal.core.SharingMetadata2.acceptAll(SharingMetadata2.java:1883)    at com.ibm.team.filesystem.client.internal.core.SharingMetadata2.acceptAll(SharingMetadata2.java:1883)    at com.ibm.team.filesystem.client.internal.core.SharingMetadata2.acceptAll(SharingMetadata2.java:1883)    at com.ibm.team.filesystem.client.internal.core.SharingMetadata2.acceptAll(SharingMetadata2.java:1883)    at com.ibm.team.filesystem.client.internal.core.SharingMetadata2.accept(SharingMetadata2.java:1845)    at com.ibm.team.filesystem.client.internal.copyfileareas.CopyFileAreaStore.accept(CopyFileAreaStore.java:2406)    at com.ibm.team.filesystem.client.internal.Shareable.accept(Shareable.java:306)    at com.ibm.team.filesystem.client.internal.localchanges.LocalChangeTracker.computePendingChanges(LocalChangeTracker.java:735)    at com.ibm.team.filesystem.client.internal.localchanges.LocalChangeManager.refreshSynchronously(LocalChangeManager.java:356)    at com.ibm.team.filesystem.client.internal.localchanges.LocalChangeManager.doRefresh(LocalChangeManager.java:394)    at com.ibm.team.filesystem.client.internal.localchanges.LocalChangeManager.refreshChanges(LocalChangeManager.java:601)    at com.ibm.team.filesystem.client.internal.localchanges.LocalChangeManager.refreshChanges(LocalChangeManager.java:584)    at com.ibm.team.filesystem.client.internal.operations.ChangeHistoryChangeSetsOperation.checkinPendingChanges(ChangeHistoryChangeSetsOperation.java:227)    at com.ibm.team.filesystem.client.internal.operations.ChangeHistoryChangeSetsOperation.checkinPendingChanges(ChangeHistoryChangeSetsOperation.java:114)    at com.ibm.team.filesystem.client.internal.operations.WorkspaceUpdateOperation.runPreConditions(WorkspaceUpdateOperation.java:976)    at com.ibm.team.filesystem.client.internal.operations.WorkspaceUpdateOperation.doAccept(WorkspaceUpdateOperation.java:802)    at com.ibm.team.filesystem.client.internal.operations.WorkspaceUpdateOperation.access$0(WorkspaceUpdateOperation.java:792)    at com.ibm.team.filesystem.client.internal.operations.WorkspaceUpdateOperation$1.run(WorkspaceUpdateOperation.java:702)    at com.ibm.team.filesystem.rcp.core.internal.resources.ResourceSharingManager$1.run(ResourceSharingManager.java:76)    at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)    at com.ibm.team.filesystem.rcp.core.internal.resources.ResourceSharingManager.runWithinFileSystemLock(ResourceSharingManager.java:88)    at com.ibm.team.filesystem.client.internal.operations.FileSystemOperation.runWithinFileSystemLock(FileSystemOperation.java:164)    at com.ibm.team.filesystem.client.internal.operations.FileSystemOperation.runWithinFileSystemLock(FileSystemOperation.java:144)    at com.ibm.team.filesystem.client.internal.operations.WorkspaceUpdateOperation.execute(WorkspaceUpdateOperation.java:714)    at com.ibm.team.filesystem.client.internal.operations.FileSystemOperation.run(FileSystemOperation.java:89)    at com.ibm.team.filesystem.client.internal.rest.util.WorkspaceUpdateUtil.workspaceUpdate(WorkspaceUpdateUtil.java:108)    at com.ibm.team.filesystem.rcp.core.internal.rest.FilesystemRestClient.postWorkspaceUpdate(FilesystemRestClient.java:798)    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)    at java.lang.reflect.Method.invoke(Method.java:618)    at com.ibm.team.filesystem.client.daemon.JSONHandler.handle(JSONHandler.java:321)    at com.ibm.team.filesystem.client.internal.http.HttpConnection.readNextRequest(HttpConnection.java:628)    at com.ibm.team.filesystem.client.internal.http.HttpConnection$1.run(HttpConnection.java:470)    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)    at com.ibm.team.repository.common.internal.marshal.util.MarshallerUtil.decodeExceptions(MarshallerUtil.java:326)    at com.ibm.team.repository.common.serialize.internal.JSONDeserializer.deserializeErrorObj(JSONDeserializer.java:957)    at com.ibm.team.repository.common.serialize.internal.JSONDeserializer.deserializeException(JSONDeserializer.java:933)    at com.ibm.team.filesystem.client.internal.marshalling.EObjectJSONDeserializer.deserializeError(EObjectJSONDeserializer.java:72)    at com.ibm.team.filesystem.client.restproxy.RestInvocationHandler.executeRequest(RestInvocationHandler.java:267)    at com.ibm.team.filesystem.client.restproxy.RestInvocationHandler.executeAndReturnResult(RestInvocationHandler.java:221)    at com.ibm.team.filesystem.client.restproxy.RestInvocationHandler.invokeInternal(RestInvocationHandler.java:368)    at com.ibm.team.filesystem.client.restproxy.RestInvocationHandler.invoke(RestInvocationHandler.java:311)    at $Proxy0.postWorkspaceUpdate(Unknown Source)    at com.ibm.team.filesystem.cli.client.internal.subcommands.AcceptCmd.run(AcceptCmd.java:152)    at com.ibm.team.filesystem.cli.core.internal.SubcommandLauncher.run(SubcommandLauncher.java:651)    at com.ibm.team.filesystem.cli.core.internal.SubcommandLauncher.doStart(SubcommandLauncher.java:398)    at com.ibm.team.filesystem.cli.core.internal.SubcommandLauncher.run(SubcommandLauncher.java:175)    at com.ibm.team.filesystem.cli.core.internal.Application.start(Application.java:39)    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)    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:368)    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:79)    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)    at java.lang.reflect.Method.invoke(Method.java:618)    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)    at org.eclipse.equinox.launcher.Main.run(Main.java:1311)Scm:An error has occurred. See the log file/home/rtc_build/sandbox/.metadata/.log.
*********************************************************************************
However if I used "scm accept -t build-workspace" out of the sandbox to accept change sets to workspace, then load the changes to the Sandbox, the operation is fine.

Does anyone can help on the "scm accept" issue?
Thanks in advance.

0 votes



One answer

Permanent link
 The exception is due to the slash in the file/directory name: AFEHRMAZ\rcinit.md5.

0 votes

Comments

I do not have any file or directory named AFEHRMAZ\rcinit.md5 or AFEHRMAZ

Can you verify that by doing a change set search for AFEHRMAZ as a file/directory name prefix? 


The stack trace that you posted can only be caused by an invalid file/directory name. Sadly the stack trace doesn't print the entire path. You could try setting a break point there and seeing what the full path is. 

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.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 1,202

Question asked: Oct 25 '12, 12:20 a.m.

Question was seen: 5,864 times

Last updated: Oct 29 '12, 9:16 a.m.

Confirmation Cancel Confirm