Thanks Peter!
That information is really useful. Just FYI, I'm working on extending
the GlassBox Inspector (which does just what you say and monitors individual
requests). I'm using the new Instrumentation package in Java 6 to find
object sizes, just the integration of all these aspects is a little tricky.
True, the information will not be super accurate, but we just need to know
when a servlet consumes vastly more resources than is normal.
Thanks for the quick reply,
Tyler
On Thu, Jun 26, 2008 at 10:11 AM, Peter Crowther <
[EMAIL PROTECTED]> wrote:
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> > I was curious if anybody knew of some software that
> > tracked the memory
> > and cpu usage of each servlet that was running on a Tomcat
> > instance.
>
> Unfortunately, as all the servlets run on a common JVM and using a common
> heap, there is no way of tracking memory use reliably (unless you want to do
> something slow and intrusive like using the debugger to trace references
> from known application roots). You *might* be able to do something about
> tracking something to do with CPU by thread, but remember that Tomcat shares
> threads between all the servlets so you'd have to do this on a per-request
> basis. I can't think of a way of persuading Java to hand over the
> information you'd need even here, but better brains on this list might have
> some ideas.
>
> In general, if you want to monitor the servlets independently, you'll have
> to run 'em on independent JVMs.
>
> - Peter
>
