Hola ;) >Okay? Expected? I don't get that. Can you point me to a email-subject of >one of those threads? Or several?!
There are a number of issues in this space. For example, if your servlet class keep a static reference, that can't be garbage collected when the webapp is recycled. Therefore the old class definition itself can't be discarded and must be kept along with its classloader in the JVM. A new classloader is created and loads new copies of your webapp classes, resulting in a total memory increase. Eventually, we made a note of this in the release notes: see the section titled "Web application reloading and static fields in shared libraries". That's one example. There are other more insidious cases. If you search the list archives (or even google) for things like "tomcat webapp reload memory leak" or "tomcat reload OutOfMemoryError" you'll see the threads and discussions, e.g. http://www.junlu.com/msg/38828.html and http://www.junlu.com/msg/13981.html. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
