-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Vicky,
On 12/14/12 2:12 PM, vicky wrote: > Thanks guys for responding, from network side there are no issues > infact as confirmed by our Network team Of /course/ the network team says that the network is fine ;) > I am accessing my application over http port, i seek your advise > on tunning my http client with respect to my tomcat Again, it's likely that your application needs to be tuned, not Tomcat. If you want to blame Tomcat for overhead, then create a trivial webapp (or use something from the 'examples' webapp) and run your load test against that. Then, you'll be tuning Tomcat and not just randomly changing things and hoping they work. > 1>>We're using MultiThreadedHttpConnectionManager, In this do you > guys have any recommendation/best practices for setting up the > parameters like maxHostConnections, maxTotalConnections,connection > timeout w.r.t tomcat Are you using Apache JMeter? Are you running it locally, or over a network? Please describe your load-test scenario. > To narrow down response time issue , i took couple of thread dumps > ,related to it i have following concerns I am getting hard time in > making sense out of thread dumps , please shed some light on my > below queries , Any weblink will be a great help :- It would help if you were to post one or those. > 2>> There were many http threads were in waiting state, is it bad > ?? That depends upon what "waiting" means in your thread dump. Different JVMs and different tools use different words for different things. Sad but true. Also, "RUNNABLE" doesn't always mean runnable, which is frustrating. > 3>> In thread dumps there are many types of thread like http > ,TP,scheduler etc > a) when request is received by tomcat which type of thread will > handle the request. The names of the threads are affected by a number of different configuration parameters. Posting the thread dump will help. It would also help to know if you have an <Executor> defined. > b) does there is a different thread type in case we're forwarding a > request from apache to Tomcat over AJP port That depends upon your configuration. Please post your <Connector> configuration(s). > c) In case if slow response respone from an application , what > ideally we should look in thread dumps Look at methods that often show up on the top of the call stack. > Does we should focus on the no. of HTTP idle threads or scheduler > threads or something else. Idle threads should not be a problem. If you have idle threads, then you either a) are not providing enough load to your webapp and you can pile more on or b) have more threads allocated than requests you are willing to accept (e.g. your thread pool is too big) - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEAREIAAYFAlDPbUcACgkQ9CaO5/Lv0PAHsQCeMfbuLSvvcX7BABjIa0vFJ/qR bvcAn2i4Oicmbyp8sfCsK7iLH0Ptn1CA =X3/R -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
