It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,865

question asked: Feb 04 '16, 4:36 p.m.
question was seen: 2,200 times
last updated: Feb 04 '16, 11:15 p.m.

Related questions

Out of memory and heap dump while running build in RTC

0
Radhakrishna Ranganathan (11●1) | asked Feb 04 '16, 4:36 p.m. 
Hi All

I installed RTC Build system toolkit and configured. When i run the build, i get heapdump and my jmv running Out of memory and build failes. Can you help on this

2016-02-04 16:22:37 [Jazz build engine]
2016-02-04 16:22:37 [Jazz build engine] Substituted the following configuration element property variables:
2016-02-04 16:22:37 [Jazz build engine]     com.ibm.team.build.cmdline : com.ibm.team.build.cmdline.arguments = -buildfile wcbd-build.xml -Dbuild.label=${buildLabel}   -->   com.ibm.team.build.cmdline.arguments = -buildfile wcbd-build.xml -Dbuild.label=20160204-1622
2016-02-04 16:22:37 [Jazz build engine]
2016-02-04 16:22:37 [Jazz build engine] running on host: stella.lexington.ibm.com
2016-02-04 16:22:37 [Jazz build engine] Should build occur?
2016-02-04 16:22:37 [Jazz build engine] Yes: Always build a user initiated request.
2016-02-04 16:22:38 [Jazz build engine] Invoking pre-build participant "com.ibm.team.build.jazzscm"
2016-02-04 16:22:38 [Jazz build engine] Accepting changes into workspace "STELLA COMMERCE Stream Workspace" ...
2016-02-04 16:22:39 [Jazz build engine] Fetching files to fetch destination "/usr/jazz/buildsystem/buildengine/eclipse/source" ...
com.ibm.team.repository.common.transport.ServiceMethodInvocationError: java.lang.OutOfMemoryError: Java heap space
    at com.ibm.team.repository.transport.client.RemoteTeamService.getAppropriateException(RemoteTeamService.java:737)
    at com.ibm.team.repository.transport.client.RemoteTeamService.executeMethod(RemoteTeamService.java:573)
    at com.ibm.team.repository.transport.client.RemoteTeamService.invoke(RemoteTeamService.java:202)
    at com.ibm.team.repository.transport.client.ServiceInvocationHandler.invoke(ServiceInvocationHandler.java:43)
    at com.sun.proxy.$Proxy28.getFileTreeByVersionable4(Unknown Source)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56)
    at java.lang.reflect.Method.invoke(Method.java:620)
    at com.ibm.team.repository.client.internal.ServiceInterfaceProxy.invokeServiceCall(ServiceInterfaceProxy.java:254)
    at com.ibm.team.repository.client.internal.ServiceInterfaceProxy.invoke(ServiceInterfaceProxy.java:110)
    at com.sun.proxy.$Proxy28.getFileTreeByVersionable4(Unknown Source)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56)
    at java.lang.reflect.Method.invoke(Method.java:620)
    at com.ibm.team.scm.client.internal.ScmServiceInterfaceProxy$2.run(ScmServiceInterfaceProxy.java:168)
    at com.ibm.team.repository.client.internal.TeamRepository$3.run(TeamRepository.java:1327)
    at com.ibm.team.repository.common.transport.CancelableCaller.call(CancelableCaller.java:79)
    at com.ibm.team.repository.client.internal.TeamRepository.callCancelableService(TeamRepository.java:1322)
    at com.ibm.team.scm.client.internal.ScmClientLibraryContext.callCancelableService(ScmClientLibraryContext.java:71)
    at com.ibm.team.scm.client.internal.ScmServiceInterfaceProxy.invokeCancelableService(ScmServiceInterfaceProxy.java:164)
    at com.ibm.team.scm.client.internal.ScmServiceInterfaceProxy.invoke(ScmServiceInterfaceProxy.java:92)
    at com.sun.proxy.$Proxy28.getFileTreeByVersionable4(Unknown Source)
    at com.ibm.team.filesystem.client.internal.FileSystemServiceProxy.getFileTreeByVersionable(FileSystemServiceProxy.java:290)
    at com.ibm.team.filesystem.client.internal.operations.LoadOperation.load(LoadOperation.java:1199)
    at com.ibm.team.filesystem.client.internal.operations.LoadOperation$1.run(LoadOperation.java:712)
    at com.ibm.team.filesystem.rcp.core.internal.resources.ResourceSharingManager$1.run(ResourceSharingManager.java:77)
    at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975)
    at com.ibm.team.filesystem.rcp.core.internal.resources.ResourceSharingManager.runWithinFileSystemLock(ResourceSharingManager.java:89)
    at com.ibm.team.filesystem.client.internal.operations.FileSystemOperation.runWithinFileSystemLock(FileSystemOperation.java:165)
    at com.ibm.team.filesystem.client.internal.operations.FileSystemOperation.runWithinFileSystemLock(FileSystemOperation.java:145)
    at com.ibm.team.filesystem.client.internal.operations.LoadOperation.execute(LoadOperation.java:750)
    at com.ibm.team.filesystem.client.internal.operations.FileSystemOperation.run(FileSystemOperation.java:90)
    at com.ibm.team.build.internal.scm.SourceControlUtility.updateFileCopyArea(SourceControlUtility.java:664)
    at com.ibm.team.build.internal.engine.JazzScmPreBuildParticipant.preBuild(JazzScmPreBuildParticipant.java:244)
    at com.ibm.team.build.internal.engine.BuildLoop.invokePreBuildParticipants(BuildLoop.java:993)
    at com.ibm.team.build.internal.engine.BuildLoop$3.run(BuildLoop.java:799)
    at java.lang.Thread.run(Thread.java:809)
Caused by: java.lang.OutOfMemoryError: Java heap space
    at com.ibm.team.repository.common.internal.marshal.impl.FastWebDemarshaller.readTag(FastWebDemarshaller.java:519)
    at com.ibm.team.repository.common.internal.marshal.impl.FastWebDemarshaller.demarshalObject(FastWebDemarshaller.java:2097)
    at com.ibm.team.repository.common.internal.marshal.impl.FastWebDemarshaller.demarshal(FastWebDemarshaller.java:2255)
    at com.ibm.team.repository.common.internal.marshal.impl.EObjectMarshaller.internalFastDemarshal(EObjectMarshaller.java:619)
    at com.ibm.team.repository.common.internal.marshal.impl.EObjectMarshaller.demarshalInputStreamToObject(EObjectMarshaller.java:580)
    at com.ibm.team.repository.transport.client.RemoteTeamService.demarshallEnvelope(RemoteTeamService.java:708)
    at com.ibm.team.repository.transport.client.RemoteTeamService.invokePost(RemoteTeamService.java:608)
    at com.ibm.team.repository.transport.client.RemoteTeamService.executeMethod(RemoteTeamService.java:548)
    ... 37 more



-rw-r--r--    1 blduser  blduser    24547992 Feb 04 15:39 core.20160204.153958.10944698.0001.dmp
-rw-r--r--    1 blduser  blduser    27323834 Feb 04 15:40 heapdump.20160204.153959.10944698.0002.phd
-rw-r--r--    1 blduser  blduser     1009568 Feb 04 15:40 javacore.20160204.153959.10944698.0004.txt
-rw-r--r--    1 blduser  blduser      961912 Feb 04 15:40 javacore.20160204.153958.10944698.0005.txt
-rw-r--r--    1 blduser  blduser    27323834 Feb 04 15:40 heapdump.20160204.153958.10944698.0003.phd
-rw-r--r--    1 blduser  blduser      240556 Feb 04 15:40 Snap.20160204.153959.10944698.0006.trc
-rw-r--r--    1 blduser  blduser       19372 Feb 04 15:40 Snap.20160204.153958.10944698.0007.trc
-rw-r--r--    1 blduser  blduser    27324758 Feb 04 15:40 heapdump.20160204.154007.10944698.0008.phd
-rw-r--r--    1 blduser  blduser      965109 Feb 04 15:40 javacore.20160204.154010.10944698.0012.txt
-rw-r--r--    1 blduser  blduser      998492 Feb 04 15:40 javacore.20160204.154007.10944698.0009.txt
-rw-r--r--    1 blduser  blduser     6589239 Feb 04 15:40 heapdump.20160204.154010.10944698.0011.phd
-rw-r--r--    1 blduser  blduser      109484 Feb 04 15:40 Snap.20160204.154010.10944698.0013.trc
-rw-r--r--    1 blduser  blduser      117676 Feb 04 15:40 Snap.20160204.154007.10944698.0010.trc



Comments
Charlie Seo commented Feb 04 '16, 5:52 p.m.

 Hi, 


I would suggest to log a PMR to the support team to revise those dump files. They need to be reviewed to find a root cause of OOM

One answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Alan Sampson (937●4●9) | answered Feb 04 '16, 11:15 p.m.
JAZZ DEVELOPER
This document https://jazz.net/wiki/bin/view/Deployment/OomIntheLog discusses the reasons for OOM errors and provides some suggestions for how to determine the root cause.  If you determine that the default memory allocation for the build engine is too small for your build you can adjust the -vmargs in the jbe.ini file.

Your answer

Register or 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.