This is interesting. Can you post a bug on this to http://nagoya.apache.org/bugzilla/ and then report back here as to what the link to that bug is? Also, it would be ideal if you could post your testcase (Foo.java) to that bug so people can easily reproduce the issue.
later,
Jake
At 12:48 PM 3/29/2003 -0700, you wrote:
I believe I'm seeing a memory leak as a result of a Manager deploy/undeploy. I have a very simple test case: a Servlet that has a static field that refers to an object (Foo) that allocates a large chunk of memory. I've instrumented both the Servlet (init(), destroy(), and finalize()) and Foo (ctor and finalize()). The Servlet has been configured to load on startup.
On a deploy, I see:
Foo.ctor (during class initialization of the Servlet) Servlet.init():
On an undeploy, I see:
Servlet.destroy() Servlet.finalize()
I never see Foo.finalize(). If I continue to deploy/undeploy repeatedly, eventually the VM reports an OutOfMemoryError when I try to deploy. Running the VM with -verbose:gc and "encouraging" GC whenever possible, I see that after each undeploy, memory usage goes up roughly by what I've allocated in Foo.
Any ideas?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
