Apache JMeter And if you use eclipse, there is a plugin project on SourceForge called EclipseColorer.
Hope there were more tutorials on how to use them though. -----Original Message----- From: Dhruva B. Reddy [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 27, 2004 9:12 AM To: Tomcat Users List Subject: RE: OutOfMemory exception explanation? I've looked for a free profiler, but was unable to find one (as in beer or speech). If you can deal with the barrage of sales calls, you can download a trial version of: JProbe: http://quest.com/jprobe/try.asp OptimizeIt: http://borland.com/products/downloads/download_optimizeit.html And...well, I forgot the third one I knew about. -d --- MURAT BALKAS <[EMAIL PROTECTED]> wrote: > > > > > > Hi, > > I need some info about these memory profiler's. Is there any > free and > easy-to-integrate-to-tomcat memory profiler? > > Thanks... > > Murat > > > > > > "Filip Hanik" > > <[EMAIL PROTECTED] To: "Tomcat > Users List" <[EMAIL PROTECTED]> > > om> cc: > > Subject: RE: > OutOfMemory exception explanation? > > 27.01.2004 01:35 > > Please respond to > > "Tomcat Users > > List" > > > > > > > > > > download a memory profiler, should give you the exact place where > memory is > being wasted. probably in your own webapp > > -----Original Message----- > From: D'Alessandro, Arthur [mailto:[EMAIL PROTECTED] > Sent: Monday, January 26, 2004 11:43 AM > To: Tomcat Users List > Subject: OutOfMemory exception explanation? > > > We've been getting these every now and then: > > Jan 23, 2004 5:03:30 PM org.apache.tomcat.util.net.TcpWorkerThread > runIt > SEVERE: Exception in acceptSocket > java.lang.OutOfMemoryError > Jan 23, 2004 5:03:30 PM > org.apache.tomcat.util.threads.ThreadPool$ControlRunnable run > SEVERE: Caught exception executing > [EMAIL PROTECTED], terminating thread > java.lang.IllegalStateException: Terminating thread > at > org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:53 > 2) > at > org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool > .java:619) > at java.lang.Thread.run(Thread.java:536) > > > > Once this occurrs, I have to stop / start the entire Tomcat container > in > order to allow this particular webapp to function again. It only > effects a particular servlet mapping for a given webapp. Does > anyone > have any suggestions on how to resolve? We're running version > 4.1.24.. > Any leads would be great, thanks. > > -Art > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free web site building tool. Try it! http://webhosting.yahoo.com/ps/sb/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
