Hi,
You're doing great work on this.  I hope you come up with additional
findings.

The guideline remains to use in-memory reloading judiciously in
production applications.  Frequently the time to restart Tomcat with a
new version of the app is only marginally more than the time to reload
the app in memory, and the former is significantly cleaner from the
JVM's perspective.

Yoav Shapira
Millennium Research Informatics


>-----Original Message-----
>From: Paulsen, Jay [mailto:[EMAIL PROTECTED]
>Sent: Thursday, September 23, 2004 12:20 PM
>To: Tomcat Users List
>Subject: RE: WebappClassLoader not garbage collected if web app used
>java.beans.Introspector
>
>I suppose Tomcat shouldn't probably do an indiscriminate flushCaches().
>It would probably have to selectively clear only the cache entries for
>classes loaded by the webapp classloader?
>
>In the end though, while this fixed by contrived web app I used in the
>testcases, it still doesn't fix my real web-app.  I'm onto the next
>library (hibernate) that seems to be pinning the webapp classloader in
>memory.  I'm begining to think that this is a lost cause.  All it takes
>is one static reference to the classloader from any code in the web app
>and the leak will occur.  I wish the classloader class had a kill()
>method that would take care of the problem ;-)
>
>Thanks for your feedback.
>
>-Jay
>
>
>> It could.  I was considering that when I attached the info
>> you posted to the relevant Bugzilla issues yesterday.  But
>> it's not trivial, because Tomcat might be using cached
>> BeanInfos from the Introspector (directly or indirectly).
>> The flushCaches would have to be done in the webapp's
>> classloader of course.  So because it's not trivial, and I
>> didn't have time to think further, I punted on the issue for
>> yesterday ;)
>>
>> Yoav
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]




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]

Reply via email to