Hi Mike, The standard-fare answer to this type of question is to get a profiler and measure where the cpu is going inside the code itself. did you not test this on your development server before launching the upgrade?
ADC > -----Original Message----- > From: Mike Scott [mailto:[EMAIL PROTECTED] > Sent: 02 September 2004 12:51 > To: [EMAIL PROTECTED] > Subject: Upgrade to 5.0.27 Causes Performance Problems > > > Upgrading to Tomcat 5.0.27 on Solaris 8, from 3.3 (a big > jump, I know), > and in live use we're seeing its CPU usage run away after a > few minutes. > If I use prstat -L to look at the individual threads, it's > java/2 that's > getting all the CPU time. If I then send the java process a SIGQUIT > signal to get it to dump a complete stack trace, I get output > including > a line like "VM Thread" prio=5 tid=0x00126830 nid=0x2 > runnable", which I > believe is the java/2 thread, but with no stack trace for that thread. > > Does anyone have any ideas about what's going on, or any other > diagnostics to try? > > -- > Mike Scott > > ______________________________________________________________ > __________ > This email has been scanned for all viruses by the > MessageLabs service. > ______________________________________________________________ > __________ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > <FONT SIZE=1 FACE="VERDANA,ARIAL" COLOR=BLUE> ------------------------------------------------------- QAS Ltd. Developers of QuickAddress Software <a href="http://www.qas.com";>www.qas.com</a> Registered in England: No 2582055 Registered in Australia: No 082 851 474 ------------------------------------------------------- </FONT> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
