Receive an error during lscm load to sandbox workspace on Linux client

DH Lee (257●8●44●46) | asked Aug 16 '13, 3:29 a.m.
JAZZ DEVELOPER
retagged Aug 20 '13, 2:41 p.m. by Te-Hsin Shih (285●4)

I have users who are using rather older Linux client and they receive error messages during lscm load.

- Linux melrhwizdev 2.4.21-63.ELsmp #1 SMP i686 i686 i386 GNU/Linux (32bit)

- Java(TM) SE Runtime Environment (build 1.6.0_18-b07)

Java HotSpot(TM) Server VM (build 16.0-b13, mixed mode)

- lscm version Build Id: RTC-I20120612-0919

Error 1. Unable to load component

# lscm load -r local -t cm_admin --force MRWTMJ_wizard_main cm_admin

Unexpected exception

java.lang.NullPointerException

at com.ibm.team.filesystem.client.internal.core.SharingMetadata2.getFileItemInfo(SharingMetadata2.java:2539)

at com.ibm.team.filesystem.client.internal.copyfileareas.CopyFileAreaStore.getLocalPathInternal(CopyFileAreaStore.java:944)

at com.ibm.team.filesystem.client.internal.copyfileareas.CopyFileAreaStore.setConfigurationState(CopyFileAreaStore.java:2992)

at com.ibm.team.filesystem.client.internal.load.MergeLoadMutator.load(MergeLoadMutator.java:824)

at com.ibm.team.filesystem.client.internal.load.MergeLoadMutator.execute(MergeLoadMutator.java:312)

at com.ibm.team.filesystem.client.internal.operations.FileSystemOperation.run(FileSystemOperation.java:89)

at com.ibm.team.filesystem.client.internal.operations.LoadOperation.load(LoadOperation.java:1047)

at com.ibm.team.filesystem.client.internal.operations.LoadOperation$1.run(LoadOperation.java:664)

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:1975)

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.LoadOperation.execute(LoadOperation.java:695)

at com.ibm.team.filesystem.client.internal.operations.FileSystemOperation.run(FileSystemOperation.java:89)

at com.ibm.team.filesystem.client.internal.rest.util.LoadUtil.load(LoadUtil.java:563)

at com.ibm.team.filesystem.rcp.core.internal.rest.FilesystemRestClient.postLoadCFA(FilesystemRestClient.java:759)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:597)

at com.ibm.team.filesystem.client.daemon.JSONHandler.handle(JSONHandler.java:322)

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:54)

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:955)

at com.ibm.team.filesystem.client.internal.marshalling.ExceptionHandlingJSONDeserializer.deserializeErrorObj(ExceptionHandlingJSONDeserializer.java:128)

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:71)

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 $Proxy1.postLoadCFA(Unknown Source)

at com.ibm.team.filesystem.cli.client.internal.subcommands.LoadCmd.run(LoadCmd.java:165)

at com.ibm.team.filesystem.cli.client.internal.subcommands.LoadCmdLauncher.run(LoadCmdLauncher.java:177)

at com.ibm.team.filesystem.cli.core.internal.SubcommandLauncher.run(SubcommandLauncher.java:673)

at com.ibm.team.filesystem.cli.core.internal.SubcommandLauncher.doStart(SubcommandLauncher.java:402)

at com.ibm.team.filesystem.cli.core.internal.SubcommandLauncher.run(SubcommandLauncher.java:179)

at com.ibm.team.filesystem.cli.client.internal.daemon.CommandLineClient.handleRequest(CommandLineClient.java:125)

at com.ibm.team.filesystem.client.internal.http.ProtocolSwitchingHttpHandler.handle(ProtocolSwitchingHttpHandler.java:46)

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:54)

java.lang.NullPointerExceptioncmbuild@melrhwizdev /home/cmbuild/workspaces/MRWTMJ_wizard_main

Error 2: Unable to load symbolic links

# lscm load -r local -t wizard --force MRWTMJ_wizard_main wizard

com.ibm.team.filesystem.client.FileSystemStatusException: Status WARNING: com.ibm.team.filesystem.client code=0 There were 2 errors. After correcting the problems, it is recommended that components be reloaded. The reload will be incremental, loading only the missing items. You can further reduce the reload time by reloading just the projects out of sync. null children=[Status WARNING: com.ibm.team.filesystem.client code=0 Unable to create symbolic link /wizard/WEBNED/build/build.properties.PROD to build.properties.PROD.NODE1 because the underlying platform does not support symbolic links null Status WARNING: com.ibm.team.filesystem.client code=0 Unable to create symbolic link /wizard/WEBNED/build/build.properties.preDomain1 to build.properties.preDomain1.NODE1 because the underlying platform does not support symbolic links null]

at com.ibm.team.filesystem.client.internal.operations.FileSystemOperation.reportErrorsAsException(FileSystemOperation.java:235)

at com.ibm.team.filesystem.client.internal.operations.FileSystemOperation.run(FileSystemOperation.java:102)