Hola, >I did a thread dump (SIG-QUIT) on both the JRun and Tomcat environments >during the "refresh button load test" and the differences are >significant.
The differences in internal thread management between any two servers are likely to be significant. >Tomcat: Java CPU% exceeds 80%. Site becomes unusable. Thread dump >yields approximately 70 threads, just over half are waiting for the DB. Maybe a connection pool problem? >I realize this test and its methodology are somewhat arbitrary, but can >ANYONE explain what Tomcat (with mod_jk or mod_jk2) is doing with its >thread management with excessive broken pipes and why the threads pile >up out of control? Can you provide a webapp and test script for us to reproduce your results? >PS. I presumed it was bad form to attach documents, but I do have >thread dumps available if anyone is willing to take a gander. Not necessarily bad form, but the list won't allow most attachment types. Snip the relevant parts of the tomcat thread dump (the JRun is useless, as the servers are completely different) and post it as a normal message, not an attachment. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
