Maven build fail with "No child processes"

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Problem

Maven build fail with the following error:

1 /opt/rh/rh-maven33/root/bin/mvn: fork: retry: No child processes

Diagnosis

Running the same maven command manually in the agent's machine works fine.

There is a difference in the environment variables MAVEN2_HOME and/or M2_HOME between the build log and agent's machine.

Resolution

Configure Maven executable path to be /opt/rh/rh-maven33/root/usr/share/maven at Administration > Build Resources > Executables

Updated on April 11, 2025
Platform
Data Center only
Product
Bamboo Data Center
On this pageProblemDiagnosisResolution

Still need help?

The Atlassian Community is here for you.
Ask the Community