Hi Sami, Here is the full console log (with some information removed for privacy sake):
Started by user anonymous Reverting /Network/Servers/server/Volumes/Data/Users/hudson/.hudson/jobs/project/workspace/trunk Updating https://server/svn/project/trunk Fetching […] Parsing POMs [trunk] $ java -Djava.awt.headless=true -cp /Network/Servers/server/Volumes/Data/Users/hudson/.hudson/plugins/maven-plugin/WEB-INF/lib/maven3-agent-1.2.jar:/usr/share/java/maven-3.0.3/boot/plexus-classworlds-2.4.jar org.jvnet.hudson.maven3.agent.Maven3Main /usr/share/java/maven-3.0.3/ /Volumes/Data/Users/hudson/.hudson/war/WEB-INF/lib/remoting-2.11.jar /Network/Servers/server/Volumes/Data/Users/hudson/.hudson/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-1.2.jar 60967 <===[JENKINS REMOTING CAPACITY]===channel started >ERROR: Maven JVM terminated unexpectedly with exit code 134 Archiving artifacts Finished: FAILURE The build is running as master. Here are the maven details from mvn --version: Apache Maven 3.0.3 (r1075438; 2011-02-28 09:31:09-0800) Maven home: /usr/share/maven Java version: 1.6.0_31, vendor: Apple Inc. Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home Default locale: en_US, platform encoding: MacRoman OS name: "mac os x", version: "10.6.8", arch: "x86_64", family: "mac" I execute jenkins with the following command as user "hudson": java -jar hudson.war --httpPort=8081 --prefix=/hudson --ajp13Port=-1 & Thanks, Mark On Saturday, May 12, 2012 11:25:30 PM UTC-7, sti wrote: > > Any chance we could see the full console log? Is the build running on the > master or slave? How did you install Jenkins? Are you using the default > maven that comes with Mac? > > -- Sami > > kirjoitti 4.5.2012 kello 22.18: > > Is anyone aware of a workaround for the Maven crash on Jenkin's build in > OS X that causes: > > <===[JENKINS REMOTING CAPACITY]===>channel started > ERROR: Maven JVM terminated unexpectedly with exit code 134 > > > In the one blog post I can find about it, > http://samuraism.jp/blog/2010/12/16/hudson_build_fails_with_maven_jvm_terminated_unexpectedly_with_exit_code_134.html, > its claimed to be an issue with Apple's JVM. The suggested workaround is > to use -Djava.awt.headless=true but this does not solve the issue for me. > > Currently on Jenkins ver. 1.447.1, but I've been having this issue on > prior versions as well. > >
