I keep expericing some slowness on a build machine that we are running. I found we have been getting daily thread dumps during the slow ness which indiciate we had a long running request which exceeeds some processing time.
Not sure what these mean but they seem to be occuring around the same time we have trouble connecting to our build machine via HTTP, or VNC. Is there anyway to diagnose if if teamcity is the cause of this slowness on the box?
Request processing time (40000 ms) exceeded for the following thread:
TC: 10:17:43 Computing artifacts state, promotion id: 36870; 10:17:43 /overview.html; POST; IP: ; http-nio-80-exec-112
TeamCity Professional 9.1.3 (build 37176)
OS: Windows 7, version 6.1, x86
JRE: 1.8.0_60, Java HotSpot(TM) Server VM (32 bit) (25.60-b23, mixed mode), Java(TM) SE Runtime Environment (1.8.0_60-b27), Oracle Corporation
JVM args: -Djava.util.logging.config.file=c:\TeamCity\bin\..\conf\logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Xrs -Xmx512m -XX:MaxPermSize=270m -Dteamcity.configuration.path=../conf/teamcity-startup.properties -Dlog4j.configuration=file:../conf/teamcity-server-log4j.xml -Dteamcity_logs=../logs/ -Djsse.enableSNIExtension=false -Djava.endorsed.dirs=c:\TeamCity\bin\..\endorsed -Dcatalina.base=c:\TeamCity\bin\.. -Dcatalina.home=c:\TeamCity\bin\.. -Djava.io.tmpdir=c:\TeamCity\bin\..\temp
Database type: MSSQL
OS: Windows 7 Professional x64, Service Pack 1
Processor: Intel Xeon CPU E5-1650 0 @ 3.20GHz
RAM: 32 GB
3 Build agents on localhost