On 10/03/2016 10:34, Theo Sweeny wrote: > Hi Mark, > ________________________________________ > From: Mark Thomas <ma...@apache.org> > Sent: 10 March 2016 10:22 > To: Tomcat Users List > Subject: Re: Tomcat 8 Shared cCassloader > > On 10/03/2016 10:19, Theo Sweeny wrote: >> Hello - I've recently noticed that there is no reference to shared.loader in >> this Tomcat How To guide seen here - >> >> https://tomcat.apache.org/tomcat-8.0-doc/class-loader-howto.html >> >> Has the shared.loader property from within catalina.properties been >> deprecated? > > No. It was removed because it was rarely used / needed. > >> If so - should shared.loader resources now be loaded via the common.loader >> instead? > > You can re-introduce the shared loader (and the catalina loader) if you > want to. > > Mark > > Thanks for the heads up. > > The motivation for asking this question is that we do have issues with web > apps classes not being removed cleanly from memory after they are undeployed, > which eventually results Perm Gen errors. > > Is it safe to say that using shared.loader would not contribute to this issue?
That isn't strictly true. Using the shared loader will (probably) mask the issue but the issue will still be there. In addition, you'll have some extra problems. Namely: - all webapps have to use exactly the same version of the JAR in the shared loader - you'll need to exclude those JARs from your build process - you'll have to stop Tomcat if you want to update the JARs in the shared loader If you can live with those restrictions then you should be OK. Personally, I'd be looking at fixing the memory leaks but that is just me. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
