Chuck, Setting the JreMemoryLeakPreventionListener attribute appContextProtection="false" also fixes the problem.
My read of documentation makes me think (1) This leak situation may arise when I use "stop" or "reload" on my webapp. (2) It can also be prevented by placing my JAI and JAI-IMAGE I/O jars in CATALINA_HOME/lib or JAVA_HOME/jre/lib/ext vs my WEB-INF/lib. Is this read correct? Regarding #2, javax.imageio.ImageIO is part of the JDK, but the readers for TIFF are loaded from jai_imageio.jar I prefer to keep the jars in my WEB-INF/lib as it's less intrusive to the server manager. --Thad On Wed, Apr 7, 2010 at 4:05 PM, Caldarale, Charles R < chuck.caldar...@unisys.com> wrote: > > From: Thad Humphries [mailto:thad.humphr...@gmail.com] > > Subject: Re: Problems with ImageIO > > > > Thanks, Chuck, Mark. That fixed it. > > There are several attributes that can be toggled on and off in the > listener; you could try those one by one, rather than disabling everything. > I suspect it's this one: appContextProtection. > > Doc is near the bottom of this page: > http://tomcat.apache.org/tomcat-6.0-doc/config/listeners.html > > - Chuck > > > THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY > MATERIAL and is thus for use only by the intended recipient. If you received > this in error, please contact the sender and delete the e-mail and its > attachments from all computers. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > -- "Hell hath no limits, nor is circumscrib'd In one self-place; but where we are is hell, And where hell is, there must we ever be" --Christopher Marlowe, 'Doctor Faustus' (v, 121-24)
