Bamboo: OutOfMemoryException during compile phase

Description

Currently Bamboo fails from time to time with a "OutOfMemoryException" during compile phase.

This needs to be fixed.

Can't stat /home/bamboo/.m2/repository: No such file or directory
at /home/bamboo/ci/bamboo/xml-data/build-dir/OPENNMS-NMS81-COMPILE/bin/functions.pl line 387.
Sep 18, 2014 4:02:08 AM org.apache.axis.utils.JavaUtils isAttachmentSupported
WARNING: Unable to find required classes (javax.activation.DataHandler and javax.mail.internet.MimeMultipart). Attachment support is disabled.
Sep 18, 2014 4:02:09 AM org.apache.axis.utils.JavaUtils isAttachmentSupported
WARNING: Unable to find required classes (javax.activation.DataHandler and javax.mail.internet.MimeMultipart). Attachment support is disabled.
Sep 18, 2014 4:07:21 AM org.apache.fop.fo.flow.ExternalGraphic bind
SEVERE: Image not available: url(images/note.png)
Sep 18, 2014 4:07:21 AM org.apache.fop.fo.flow.ExternalGraphic bind
SEVERE: Image not available: url(images/note.png)
Sep 18, 2014 4:07:21 AM org.apache.fop.fo.flow.ExternalGraphic bind
SEVERE: Image not available: url(images/note.png)
Sep 18, 2014 4:07:21 AM org.apache.fop.fo.flow.ExternalGraphic bind
SEVERE: Image not available: url(images/note.png)
Sep 18, 2014 4:07:21 AM org.apache.fop.layoutmgr.inline.LineLayoutManager$LineBreakingAlgorithm updateData2
WARNING: Line 1 of a paragraph overflows the available area. (fo:block, location: 194/605)
Sep 18, 2014 4:07:21 AM org.apache.fop.fo.flow.ExternalGraphic bind
SEVERE: Image not available: url(images/note.png)
Sep 18, 2014 4:07:21 AM org.apache.fop.fo.flow.ExternalGraphic bind
SEVERE: Image not available: url(images/note.png)
Sep 18, 2014 4:07:21 AM org.apache.fop.fo.flow.ExternalGraphic bind
SEVERE: Image not available: url(images/note.png)
Sep 18, 2014 4:12:42 AM org.apache.axis.utils.JavaUtils isAttachmentSupported
WARNING: Unable to find required classes (javax.activation.DataHandler and javax.mail.internet.MimeMultipart). Attachment support is disabled.
Sep 18, 2014 4:12:43 AM org.apache.axis.utils.JavaUtils isAttachmentSupported
WARNING: Unable to find required classes (javax.activation.DataHandler and javax.mail.internet.MimeMultipart). Attachment support is disabled.
Exception in thread "Thread-13" java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Arrays.java:2367)
at java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:130)
at java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:114)
at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:415)
at java.lang.StringBuffer.append(StringBuffer.java:237)
at org.codehaus.plexus.util.cli.CommandLineUtils$StringStreamConsumer.consumeLine(CommandLineUtils.java:52)
at org.codehaus.plexus.util.cli.StreamPumper.consumeLine(StreamPumper.java:190)
at org.codehaus.plexus.util.cli.StreamPumper.run(StreamPumper.java:135)

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Benjamin Reed September 26, 2014 at 11:06 AM

I forgot to put this "in-progress" – I investigated it and it was actually the bamboo agent that was getting an OOM, probably while parsing particularly large amounts of log data. I've bumped all our bamboo agents to use 512m instead of 384m at startup and this problem seems to be fixed now.

Seth Leger September 18, 2014 at 3:42 PM

I've seen this on my own machine outside of Bamboo. I'm not sure what Bamboo is set to but using -Xmx1g usually fixes the problem for me.

Benjamin Reed September 18, 2014 at 12:23 PM

Do you have a link to the build that failed? I'd like more information on which part is getting the OOM. Your log looks like the "summary" failure log which doesn't contain the whole output.

Fixed

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

PagerDuty

Created September 18, 2014 at 4:36 AM
Updated March 17, 2015 at 5:42 PM
Resolved September 26, 2014 at 11:06 AM

Flag notifications