On Fri, Jan 24, 2014 at 02:50:54PM +0000, Santhosh Edukulla wrote: > Team, > > Simulator-build Job failing with log @ > http://jenkins.buildacloud.org/view/simulator/job/simulator-build/lastBuild/console > as below. Please let us know if we can do something to bring this job up. > > CATALINA_HOME=/usr/share/apache-tomcat-6.0.33 > ++ export M2_HOME=/usr/share/apache-maven-3.0.5 > ++ M2_HOME=/usr/share/apache-maven-3.0.5 > ++ export > PATH=/usr/share/apache-maven-3.0.5/bin:/usr/share/apache-maven-3.0.5/bin:/usr/local/bin:/bin:/usr/bin > ++ > PATH=/usr/share/apache-maven-3.0.5/bin:/usr/share/apache-maven-3.0.5/bin:/usr/local/bin:/bin:/usr/bin > ++ export 'MAVEN_OPTS=-Xmx1024m -XX:MaxPermSize=500m' > ++ MAVEN_OPTS='-Xmx1024m -XX:MaxPermSize=500m' > + mvn -Pdeveloper -Dsimulator -DskipTests clean install > Error occurred during initialization of VM > Cannot create VM thread. Out of system resources. > Build step 'Execute shell' marked build as failure > Finished: FAILURE
All the failing jobs may have launched too many JVMs and eaten up resources. Would need to login to the simulator slave on jenkins and kill the hung jobs. Ideally, stop-jetty job will stop the started java instance of the management server, but I think someone may have removed that target which Ian had put in a while ago. > > > Thanks! > Santhosh -- Prasanna., ------------------------ Powered by BigRock.com
