> > Personally, I'd like to have memory footprint data recorded and
> > multithreading/scalability/errorhandling improved.
> It is difficult to check memory footprint in java. The only way is
> to limit the JVM resources and see how it works.
But we can still use the heapdump tools to check for memory leaks. I do
that prior to releases, and whenever something seems to be leaking. We
cannot do anything about what the underlying JVM does, but we can see the
objects being created, destroyed, preserved and their allocation sites.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
