tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shanti Suresh <sha...@umich.edu>
Subject Re: common vs system vs shared class loaders
Date Thu, 17 Jan 2013 18:48:04 GMT
Hi Chuck, Dan,

Sometimes, sharing classes across applications may become necessary
though.  We have a situation where a separate application and associated
webapp classloader is launched for each site in our application.  The
reason this is happening is because things have been setup differently
internally - without going into too many details.  So, we ran into PermGen
exhaustion issues.  Putting all the libraries in $CATALINA_HOME/common/lib"
and modifying the common classloader in catalina.properties as follows,
ensures that a single copy of the classes get loaded and shared among all
sites:

common.loader=${catalina.base}/lib,${catalina.base}/lib/*.jar,${catalina.home}/lib,${catalina.home}/lib/*.jar,${catalina.base}/common/lib/*.jar

We wanted to also put the libraries into a separate directory called
"common/" because we wanted to keep them separate from the Tomcat-native
libraries.

He may have a similar situation too; don't know.

Regards,

                  -Shanti


On Thu, Jan 17, 2013 at 10:58 AM, Daniel Mikusa <dmikusa@vmware.com> wrote:

> On Jan 17, 2013, at 10:26 AM, Caldarale, Charles R wrote:
>
> >> From: Narahari 'n' Savitha [mailto:savithari@gmail.com]
> >> Subject: Re: common vs system vs shared class loaders
> >
> >> Sorry Dan but if I do what you are suggesting I will end up in redundant
> >> jars all over the place and I dont want to do that.
> >
> > That's an issue easily handled by a deployment script.  You really,
> really, really do not want to share classes across webapps.
> >
> > - Chuck
> >
>
> +1
>
> Dan
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message