Out of memory exception while loading the workspace
I have started loading the workspace using the below command
sh /opt/jazz/scmtools/eclipse/scm.sh load Conn-Reg-WS -r https://ips-rtc.swg.usma.ibm.com/jazz/ Regression_Suite -d /opt/conn_reg As the result of execution above command, it started downloading files into workspace. Later after some time it failed with below error Downloading /Connectors/qa/functional/test/=/opt/IBM/InformationServer/Server/Projects/DB2CC_NEW/db2ccupsert_input/upsert.txt (506 B) Downloading /Connectors/qa/functional/test/=/opt/IBM/InformationServer/Server/Projects/ZDB2CC/zinputs/input1.txt (9.3 KB) Downloading /Plug-Ins/Framework/dsplugins/util/test/src/com/ascentialsoftware/test/plugin/xmlpack/XMLPackStageTestCase.java (3.3 KB) JVMDUMP006I Processing dump event "systhrow", detail "java/lang/OutOfMemoryError" - please wait. JVMDUMP032I JVM requested Snap dump using '/opt/conn_reg/Snap.20130512.102004.30526.0001.trc' in response to an event JVMDUMP010I Snap dump written to /opt/conn_reg/Snap.20130512.102004.30526.0001.trc JVMDUMP032I JVM requested Heap dump using '/opt/conn_reg/heapdump.20130512.102004.30526.0002.phd' in response to an event JVMDUMP010I Heap dump written to /opt/conn_reg/heapdump.20130512.102004.30526.0002.phd JVMDUMP032I JVM requested Java dump using '/opt/conn_reg/javacore.20130512.102004.30526.0003.txt' in response to an event JVMDUMP010I Java dump written to /opt/conn_reg/javacore.20130512.102004.30526.0003.txt JVMDUMP013I Processed dump event "systhrow", detail "java/lang/OutOfMemoryError". Unexpected exception java.lang.OutOfMemoryError at org.eclipse.core.runtime.Path.append(Path.java:242) at com.ibm.team.filesystem.client.internal.PathLocation.append(PathLocation.java:64) at com.ibm.team.filesystem.rcp.core.internal.resources.ResourceStorageManager.findImportedResource(ResourceStorageManager.java:240) at com.ibm.team.filesystem.rcp.core.internal.resources.ResourceStorageManager.resolveFileStorage(ResourceStorageManager.java:213) at com.ibm.team.filesystem.client.internal.SharingManager.resolveFileStorage(SharingManager.java:925) at com.ibm.team.filesystem.client.internal.FileStorageWrapper.getUnderlyingStorage(FileStorageWrapper.java:102) at com.ibm.team.filesystem.client.internal.FileStorageWrapper.refreshCachedSubTree(FileStorageWrapper.java:736) at com.ibm.team.filesystem.client.internal.load.MergeLoadMutator$2.run(MergeLoadMutator.java:1251) at com.ibm.team.filesystem.client.internal.SharingManager.doSilentChange(SharingManager.java:642) at com.ibm.team.filesystem.client.internal.load.MergeLoadMutator.refresh(MergeLoadMutator.java:1248) at com.ibm.team.filesystem.client.internal.load.MergeLoadMutator.updateContentLoadedMetaData(MergeLoadMutator.java:1185) at com.ibm.team.filesystem.client.internal.load.MergeLoadMutator.load(MergeLoadMutator.java:740) at com.ibm.team.filesystem.client.internal.load.MergeLoadMutator.execute(MergeLoadMutator.java:291) 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:939) at com.ibm.team.filesystem.client.internal.operations.LoadOperation$1.run(LoadOperation.java:593) 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.LoadOperation.execute(LoadOperation.java:624) at com.ibm.team.filesystem.client.internal.operations.FileSystemOperation.run(FileSystemOperation.java:89) at com.ibm.team.filesystem.cli.client.internal.subcommands.LoadCmd.run(LoadCmd.java:237) at com.ibm.team.filesystem.cli.client.internal.subcommands.LoadCmdLauncher.run(LoadCmdLauncher.java:193) 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) at org.eclipse.equinox.launcher.Main.main(Main.java:1287) [dsadm@isodvm11 conn_reg]$ I am performing this operation on RHEL 6.2 KVM system. Thanks, Nagesh Mandava. |
2 answers
Hi Nagesh
Looks like you have run out of memory in the JVM. The SCM tools are installed as part of the build tools - so look in <install dir>\scmtools\eclipse and find the file called scm.ini. There should be an entry like this: -Xmx512m Increase this number to something like: -Xmx1024m I am assuming you have lots of physical or virtual machine memory. As a general rule, keep this setting to less than half the amount of physical memory on the machine. anthony Comments Hi Anthony,
|
Hi Mandava,
It seems to be a new defect in RTC. Consider creating new defect on https://jazz.net/jazz/web/projects/Rational Team Concert#action=com.ibm.team.workitem.newWorkItem&type=defect |
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.