Summary

When using Maven v3.0.5 on CentOS 7, the Maven task spawns thousands of mvn processes, which eventually use up all of the available RAM and swap space. Notably, this does not occur when running the Maven command with a Script task.

Environment

• CentOS 7.3
• Apache Maven 3.0.5 (Red Hat 3.0.5-17)

Expected Results

Maven successfully builds and tests the executable

Actual Results

The build forks and runs out of swap space
The below exception is thrown in CentOS's messages log file:

Out of memory: Kill process <java pid> (java) score 332 or sacrifice child

Workaround

Option 1

Upgrade Maven to 3.5.0 or higher

Option 2

Run the Maven command in a Script task
<GOAL> is the contents of the Goal field in the Maven Task configuration

 /path/to/mvn --batch-mode <GOAL>