----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files. Don't make us guess your problem!!!
----------------------------------------------------------------
> Also, I don't really know how to debug memory leaks in Java at all... any
hints?
The most common cause of a memory leak in Java is a container to which
objects are added and not removed as expected. For example, you may have an
array or Vector that grows without bounds simply because your logic for
removing objects is flawed (or bypassed, as in an exception condition). At
some point, then, you'll obviously run out of memory. Some of the core Java
libraries (particulary Swing, which doesn't apply to Servlets of course)
have had (and my continue to have -- I'm not sure) memory leaks of this
fashion.
Unfortunately I don't know of an easy way to combat this problem. Assuming
you haven't wrapped the core container classes with your own container
library (which would allow you to insert debugging code), you'll have to
search for your uses of container classes one by one and verify that they're
being depopulated as you expect. In particular, look for code that may be
bypassed due to exception conditions; in these cases, a finally clause may
be necessary.
Hope this helps.
David
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
