I have a barebones TeamCity 8.1.2 installation on my MacbookPro (OSX 10.9.2 Java 1.6 / 1.7), it's functioning as the server + agent. I setup 1 project with 1 build (bash script) using Github (no commit hooks though) to do Unity3d command line builds.
After I configured my project & build steps I noticed that the java process from teamcity was using 50-70% CPU while idling. I did some googling and nothing came up so I decided to post here.
start command output:
Taylors-MacBook-Pro:TeamCity taylor$ ./bin/runAll.sh start
Using CATALINA_BASE: /Applications/TeamCity
Using CATALINA_HOME: /Applications/TeamCity
Using CATALINA_TMPDIR: /Applications/TeamCity/temp
Using JRE_HOME: /System/Library/Frameworks/JavaVM.framework/Home
Using CLASSPATH: /Applications/TeamCity/bin/bootstrap.jar:/Applications/TeamCity/bin/tomcat-juli.jar
Starting TeamCity build agent...
Java executable is found in '/System/Library/Frameworks/JavaVM.framework/Home'.
Starting TeamCity Build Agent Launcher...
Agent home directory is /Applications/TeamCity/buildAgent
Current Java runtime version is 1.7
Lock file: /Applications/TeamCity/buildAgent/logs/buildAgent.properties.lock
Using no lock
Done , see log at /Applications/TeamCity/buildAgent/logs/teamcity-agent.log
this is the process that is using the cpu:
501 81052 1 0 1:51PM ttys003 1:56.88 /System/Library/Frameworks/JavaVM.framework/Home/bin/java -Djava.util.logging.config.file=/Applications/TeamCity/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -server -Xmx512m -XX:MaxPermSize=270m -Dlog4j.configuration=file:/Applications/TeamCity/bin/../conf/teamcity-server-log4j.xml -Dteamcity_logs=../logs/ -Djava.awt.headless=true -Djava.endorsed.dirs=/Applications/TeamCity/endorsed -classpath /Applications/TeamCity/bin/bootstrap.jar:/Applications/TeamCity/bin/tomcat-juli.jar -Dcatalina.base=/Applications/TeamCity -Dcatalina.home=/Applications/TeamCity -Djava.io.tmpdir=/Applications/TeamCity/temp org.apache.catalina.startup.Bootstrap start
the start and stop logs from /Applications/TeamCity/buildAgent/logs/* and /Applications/TeamCity/logs/*
I'm assuming this is not supposed to happen. Any ideas what it might be? How can I debug this further?
I tried switching my JRE_HOME to java 1.7 (from java 1.6) but there was no change.
I'm a programmer but have never done anything with Java so I don't quite know where to start debugging this. The misbehaving process seems to be Tomcat, which I know is the java application server, but I don't know how to dig deeper.