We have noticed the CPU usage of TeamCity increased rather substantially in the last week and it looks to have started at midnight on July the 1st for some reason.
$ ps -ea -o pcpu,cmd | grep teamcity
246 /usr/bin/java -Djava.util.logging.config.file=/opt/TeamCity/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -server -Xmx512m -XX:MaxPermSize=270m -Dlog4j.configuration=file:/opt/TeamCity/bin/../conf/teamcity-server-log4j.xml -Dteamcity_logs=../logs/ -Djava.awt.headless=true -Djava.endorsed.dirs=/opt/TeamCity/endorsed -classpath /opt/TeamCity/bin/bootstrap.jar:/opt/TeamCity/bin/tomcat-juli.jar -Dcatalina.base=/opt/TeamCity -Dcatalina.home=/opt/TeamCity -Djava.io.tmpdir=/opt/TeamCity/temp org.apache.catalina.startup.Bootstrap start
We had been running 7.0.2 and the HSQLDB so we have migrated to a local MySQL database and upgraded to 7.0.3 (after reading through http://youtrack.jetbrains.com/issue/TW-21375
We also upgraded java to version 1.7.0 incase there was any issues with the java release.
# /usr/lib/jvm/jre-1.6.0-openjdk.x86_64/bin/java -version
java version "1.6.0_17"
OpenJDK Runtime Environment (IcedTea6 1.7.9) (rhel-1.36.b17.el6_0-x86_64)
OpenJDK 64-Bit Server VM (build 14.0-b16, mixed mode)
# /usr/java/jdk1.7.0_05/bin/java -version
java version "1.7.0_05"
Java(TM) SE Runtime Environment (build 1.7.0_05-b05)
Java HotSpot(TM) 64-Bit Server VM (build 23.1-b03, mixed mode)
None of these have resolved the problem so its still sitting there sucking CPU time.
Are there any further solutions that we could try?