Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-5144

Mysterious Maven JVM launch failure with exit code 143

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: maven-plugin
    • Labels:
      None

      Description

      I see random test failures with errors like this:

      [workspace] $ /files/hudson/tools/linux-amd64/java1.6.0_13/jre/bin/java -cp /files/hudson/workspace/hudson-trunk/maven-agent/target/maven-agent-1.339-SNAPSHOT.jar:/tmp/hudson2645431271863489887test/apache-maven-2.2.1/boot/classworlds-1.1.jar hudson.maven.agent.Main /tmp/hudson2645431271863489887test/apache-maven-2.2.1 /files/hudson/workspace/hudson-trunk/remoting/target/remoting-1.339-SNAPSHOT.jar /files/hudson/workspace/hudson-trunk/maven-interceptor/target/maven-interceptor-1.339-SNAPSHOT.jar 51346 /files/hudson/workspace/hudson-trunk/.m2/org/jvnet/hudson/maven2.1-interceptor/1.2/maven2.1-interceptor-1.2.jar
      ERROR: Failed to launch Maven. Exit code = 143
      

      This is an attempt to collect more information about this error.

        Activity

        Hide
        jchristi jchristi added a comment -

        I seem to get this much more frequently if I use the Hudson M2 Extra Steps Plugin and use it in my build. As soon as I disabled it from my build, the job succeeded without a problem.

        Show
        jchristi jchristi added a comment - I seem to get this much more frequently if I use the Hudson M2 Extra Steps Plugin and use it in my build. As soon as I disabled it from my build, the job succeeded without a problem.
        Hide
        clecompt clecompt added a comment -

        I believe this is related to the behavior of the logout process on Microsoft Windows. When a logout from the console occurs Windows attempts to kill all processes spawned from the console including those spawned by a cmd.exe executable. I get this issue if a build is currently running and I log out. The use of the -Xrs flag when launching the java process should eliminate this issue.

        Show
        clecompt clecompt added a comment - I believe this is related to the behavior of the logout process on Microsoft Windows. When a logout from the console occurs Windows attempts to kill all processes spawned from the console including those spawned by a cmd.exe executable. I get this issue if a build is currently running and I log out. The use of the -Xrs flag when launching the java process should eliminate this issue.
        Hide
        dermoritz mo loe added a comment -

        i just stumbled over this bug: right after i restarted the host-vm (esxi hosting win 2003 server, tomcat 7.0.20, jenkins 1.433) to give it 2 additional cpu cores. but it isn't reproducible. on the second try clicking "build now" it worked fine.

        Show
        dermoritz mo loe added a comment - i just stumbled over this bug: right after i restarted the host-vm (esxi hosting win 2003 server, tomcat 7.0.20, jenkins 1.433) to give it 2 additional cpu cores. but it isn't reproducible. on the second try clicking "build now" it worked fine.
        Hide
        zigarn Alexandre Garnier added a comment -

        I reproduce this every time I log off from the Remote Desktop on server under windows XP running Jenkins in Tomcat as service: all jobs are stopped with message:

        ERROR: Maven JVM terminated unexpectedly with exit code 143
        

        Adding the -Xrs flag in global MAVEN_OPTS solved the problem.

        Show
        zigarn Alexandre Garnier added a comment - I reproduce this every time I log off from the Remote Desktop on server under windows XP running Jenkins in Tomcat as service: all jobs are stopped with message: ERROR: Maven JVM terminated unexpectedly with exit code 143 Adding the -Xrs flag in global MAVEN_OPTS solved the problem.
        Hide
        jchappelle Josh Chappelle added a comment -

        We have been getting this for quite some time. We have Jenkins nodes running on CentOS linux. It only happens when we have two or more builds running at the same time. We are using the maven plugin for our builds. Our builds completely delete the workspace afterwards and checks out the entire source code into a separate workspace each time the build is run. Not sure if that is relevant but I just wanted to put any information that might help.

        Show
        jchappelle Josh Chappelle added a comment - We have been getting this for quite some time. We have Jenkins nodes running on CentOS linux. It only happens when we have two or more builds running at the same time. We are using the maven plugin for our builds. Our builds completely delete the workspace afterwards and checks out the entire source code into a separate workspace each time the build is run. Not sure if that is relevant but I just wanted to put any information that might help.

          People

          • Assignee:
            Unassigned
            Reporter:
            kohsuke Kohsuke Kawaguchi
          • Votes:
            5 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

            • Created:
              Updated: