[BUILD-91] OutOfMemoryError when running ee-bundle Created: 01/Feb/12 Updated: 13/Apr/17 Resolved: 09/Feb/12 |
|
| Status: | Closed |
| Project: | Build |
| Component/s: | None |
| Affects Version/s: | POMs 20 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical |
| Reporter: | Daniel Lipp | Assignee: | Daniel Lipp |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Template: |
|
||||
| Acceptance criteria: |
Empty
|
||||
| Description |
|
We regularly get OOME when building the ee-bundle on hudson. Increasing memory in MAVEN_OPTS (e.g. to 2048) did not help. Example: http://hudson.magnolia-cms.com/view/X/job/ee_bundle/1771/consoleFull |
| Comments |
| Comment by Daniel Lipp [ 03/Feb/12 ] |
|
Caution: even when build is show as success we might have run into OOME (there's many logs of successful builds containing OOME). So it basically depends on when the OOME happens. |
| Comment by Daniel Lipp [ 03/Feb/12 ] |
|
Locally OOME will also occur in case you didn't set your $JAVA_OPTS and $MAVEN_OPTS (as described e.g. in the release process). |
| Comment by Daniel Lipp [ 03/Feb/12 ] |
|
Looks like upgrading the clover-maven2-plugin solves the problem. Unfortunately the latest version (1.2.0) does not properly output all cargo/jetty stuff to maven console so we went for 1.1.4 (also passed the jvm args properly) |