Hello Try to do a java thread dump and check the stuck threads (possibly by comparing with the output of the tomcat server status page). Hopefully this will give you a clue about what the threads are doing at that time. If the application uses a database, you may see that they are stuck waiting for the dB reply. It could also be that it's waiting for disk (perhaps you have too much logging enabled) etc.
How do you simulate your users and do you have proper timing between requests of each users? If a real user on average take 10 seconds between requests and you have a timing of 1 second between requests in your load test, you are simulating 10x the load you think.. Br L On 7 Apr 2015 18:56, "PerfGuru" <myunipor...@yahoo.com.invalid> wrote: > Hi All,We are noticing when running a simple load test of 25 virtual users > that our Tomcat server is running at 40% CPU and transactions are taking > over 40 seconds. We setup a test where we focused (in a loop) one of the > longer response time requests. The access logs show the log response time > and the developers have monitoring via their own logs where they record > response times for queries and other things but do not show the response > times as being nearly as long as the access logs indicate.We connected up > visualvm 1.3.7 remotely and using the sampler the only method response time > above 2 seconds on average was the TaskQuery.take() which was over 100 > seconds for some reason.We are using some version of 7.x for tomcat and > also for the jdk. The tomcat config file is shown below. We are in the > process of setting up visualvm on the unix server where Tomcat is running > so we can use local mode for visualvm instead of remote. > Any ideas/thoughts appreciated.-Tony > > > <Connector port="25500" secure="true" > compressableMimeType="text/html,text/xml" noCompressionUserAgents="gozilla, > traviata" compression="on" disableUploadTimeout="true" > connectionTimeout="20000" acceptCount="100" redirectPort="8443" > enableLookups="false" minSpareThreads="25" maxThreads="512" > maxHttpHeaderSize="8192"/> > >
