[Nice description of leak problem removed]
>Failing that, any suggestions on how to investigate this sort of problem
>would be appreaciated. I did manage to get the JSWDK 1.0 ea running
>under the JProbe evaluation, but I could not find anything conclusive,
>due to my lack of expertise with the product. It looks like I may have
>to invest some more time there....
The easiest way to debug memory leaks is to get a heap analyzer. OptimizeIt
makes a good one, and there's also the HAT tool from JavaSoft, which is more
primitive. These tools will allow you to click through your graphs of
objects (with even better detail using a 1.2 JDK).
Hope you find the problem,
Mike
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
