Thanx 4 you answer; ps: there are 100 webservices, not webapps Pls, help me: I'm not a developer ... and I don't understand the disadvantages of "static classes/fields loaded from common classloader will be shared among all webapps", Could you be a little more specific about the disadvantages? Your suggestion is to "split" the apps into vitualhost like, context.xml ecc..? I use the oracle odbc thin; which problem should I have putting the jdbc driver int the commos/lib ? For reference, those are the jars userd in all webservices: classes12.jar ibatis-common-2.jar ibatis-dao-2.jar ibatis-sqlmap-2.jar activation.jar axis-ant.jar axis.jar commons-discovery-0.2.jar commons-logging-1.0.4.jar jaxrpc.jar LEGO_CONDIVISI.jar log4j-1.2.8.jar mail.jar saaj.jar wsdl4j-1.5.1.jar xmlsec-1.4.0.jar Michele
On Wed, Nov 4, 2009 at 11:00 AM, Mikolaj Rydzewski <m...@ceti.pl> wrote: > Michele Mase' wrote: > >> I've 100 webapps on one single tomcat instance. >> Every webapps has in his WEB-INF/lib the same jars >> I've some permgen memory problems too >> Moving all the shared libs in tomcat's root/common/lib should help me >> reducing the perm gen memory usage? >> Should it be a good pratics >> > It will solve one problem, but will cause others, difficult to trace. E.g. > static classes/fields loaded from common classloader will be shared among > all webapps. > You should rather refactor your webapp to be able to change its 'work > context' depending on URI/domain name. > > -- > Mikolaj Rydzewski <m...@ceti.pl> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
