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

Getting Internal Error Exception when running cli load in RTC 4.0.5

I have run into a very odd error when loading specific components with baselines using the CLI.  The script was working fine in the past and all of a sudden, certain components have generated this error.  The odd part is that in different streams, it is different components that generate this error.  This is preventing us from being about to reliably build our components.  I am including the log of the error as well as the script I am running.

Error:

$ /data/scripts/build/rtc_dev_build_checkout.sh portal R4.0.0_Dev R4.0.0_Dev_Workspace_Build /export/home/builduser/.jenkins/workspace/DEV-R4.0.0_Portal_Build_Deploy
Logged in to https://myhostname.com:9443/ccm
Executing command: /opt/IBM/RTC_4.0.5/jazz/scmtools/eclipse/lscm accept -s R4.0.0_Dev -t R4.0.0_Dev_Workspace_Build -r https://myhostname.com:9443/ccm
Workspace unchanged.
Executing command: /opt/IBM/RTC_4.0.5/jazz/scmtools/eclipse/lscm load -L /data/build/loadrules/portal_dev.loadrule R4.0.0_Dev_Workspace_Build -d /export/home/builduser/.jenkins/workspace/DEV-R4.0.0_Portal_Build_Deploy -r https://myhostname.com:9443/ccm
Unexpected exception
com.ibm.team.rtc.cli.infrastructure.internal.core.CLIClientException: Internal error
        at com.ibm.team.filesystem.cli.core.util.StatusHelper.toCLIClientException(StatusHelper.java:717)
        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:569)
        at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.doStart(SubcommandLauncher.java:365)
        at com.ibm.team.rtc.cli.infrastructure.internal.core.SubcommandLauncher.run(SubcommandLauncher.java:129)
        at com.ibm.team.filesystem.cli.client.internal.daemon.CommandLineClient.handleRequest(CommandLineClient.java:186)
        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)
Caused by: java.lang.IllegalArgumentException
        at com.ibm.team.internal.repository.rcp.dbhm.DiskBackedHashMap$Entry.<init>(DiskBackedHashMap.java:924)
        at com.ibm.team.internal.repository.rcp.dbhm.CachedDiskBackedHashMap$CachedEntry.<init>(CachedDiskBackedHashMap.java:263)
        at com.ibm.team.internal.repository.rcp.dbhm.CachedDiskBackedHashMap.createEntry(CachedDiskBackedHashMap.java:206)
        at com.ibm.team.internal.repository.rcp.dbhm.DiskBackedHashMap.getEntry(DiskBackedHashMap.java:534)
        at com.ibm.team.internal.repository.rcp.dbhm.CachedDiskBackedHashMap.getEntry(CachedDiskBackedHashMap.java:136)
        at com.ibm.team.internal.repository.rcp.dbhm.DiskBackedHashMap.getEntry(DiskBackedHashMap.java:491)
        at com.ibm.team.internal.repository.rcp.dbhm.CachedDiskBackedHashMap.getEntry(CachedDiskBackedHashMap.java:109)
        at com.ibm.team.internal.repository.rcp.dbhm.DiskBackedHashMap.containsKey(DiskBackedHashMap.java:147)
        at com.ibm.team.filesystem.client.internal.core.SharingMetadata2.isLoaded(SharingMetadata2.java:3117)
        at com.ibm.team.filesystem.client.internal.copyfileareas.CopyFileAreaStore.internalIsLoaded(CopyFileAreaStore.java:3069)
        at com.ibm.team.filesystem.client.internal.copyfileareas.CopyFileAreaManager.getCopyFileAreasForConfiguration(CopyFileAreaManager.java:476)
        at com.ibm.team.filesystem.client.internal.SharingManager.getSandboxes(SharingManager.java:1146)
        at com.ibm.team.filesystem.client.internal.operations.LoadOperation.getConfigurationSandboxes(LoadOperation.java:732)
        at com.ibm.team.filesystem.client.internal.operations.LoadOperation.getMultipleSandboxLoads(LoadOperation.java:410)
        at com.ibm.team.filesystem.client.internal.rest.util.LoadUtil.evaluateLoad(LoadUtil.java:158)
        at com.ibm.team.filesystem.rcp.core.internal.rest.FilesystemRestClient.getLoadCFA(FilesystemRestClient.java:667)
        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:340)
        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.getLoadCFA(Unknown Source)
        at com.ibm.team.filesystem.cli.client.internal.subcommands.LoadCmd.evaluateLoad(LoadCmd.java:504)
        at com.ibm.team.filesystem.cli.client.internal.subcommands.LoadCmd.run(LoadCmd.java:161)
        at com.ibm.team.filesystem.cli.client.internal.subcommands.LoadCmdLauncher.run(LoadCmdLauncher.java:177)
        at com.ibm.team.filesystem.cli.core.AbstractSubcommand.run(AbstractSubcommand.java:51)
        ... 8 more
java.lang.RuntimeException: com.ibm.team.rtc.cli.infrastructure.internal.core.CLIClientException: Internal error
Script:
#!/bin/bash

component=${1}
stream=${2}
build_workspace=${3}
jenkins_workspace=${4}

RTC_URL="https://myhostname.com:9443/ccm"
SCM_TOOLS_PATH="/opt/IBM/RTC_4.0.5/jazz/scmtools/eclipse"
build_user=*Masked Username*
build_password=*Masked Password*
LOADRULES_PATH="/data/build/loadrules"

${SCM_TOOLS_PATH}/lscm login -r ${RTC_URL} -u ${build_user} -P ${build_password}
echo "Executing command: ${SCM_TOOLS_PATH}/lscm accept -s ${stream} -t ${build_workspace} -r ${RTC_URL}"
${SCM_TOOLS_PATH}/lscm accept -s ${stream} -t ${build_workspace} -r ${RTC_URL}
echo "Executing command: ${SCM_TOOLS_PATH}/lscm load -L ${LOADRULES_PATH}/${component}_dev.loadrule ${build_workspace} -d ${jenkins_workspace} -r ${RTC_URL}"
${SCM_TOOLS_PATH}/lscm load -L ${LOADRULES_PATH}/${component}_dev.loadrule ${build_workspace} -d ${jenkins_workspace} -r ${RTC_URL}
#${SCM_TOOLS_PATH}/lscm logout -r ${RTC_URL}
Thanks,

Brandon

0 votes

Comments

Is the directory you are loading to empty or is it a sandbox that is already tracked by RTC? If it is a sandbox, can you try loading to a new directory and see if it works?


Be the first one to answer this question!

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

Question asked: Feb 28 '14, 7:10 p.m.

Question was seen: 8,773 times

Last updated: Mar 02 '14, 10:36 p.m.

Confirmation Cancel Confirm