Hi Ray, It is one JVM, but separate classloaders so applications do not "see" classes of other apps.
Oh and please be extremely careful with using System.gc(). Using it can lead to severe and unexpected performance issues. If you "need" gc() you almost always have a flaw in your code. Cheers, Kees de Kooter http://www.boplicity.net On Mon, Feb 2, 2009 at 13:59, Ray Holme <rho...@roadrunner.com> wrote: > I run tomcat 6 on Linux and have multiple applications in development > mode. From my testing I have discovered that a Java bean shared by all > applications and with ALL methods as static SEEMS to have a separate > instance for each appliction - i.e. > > getDebugLevel() returns 0 from the 2nd application > even if the first has set it to 100 > > This is useful but contrary to what I would expect. I would expect one > JVM for all applications. If there is one per application, that too is > cool, but it means that each application must do a > > System.gc() > > occasionally and that this routine cannot be done once for all. > > So, does someone know for sure - one JVM per Tomcat OR one JVM per app?? > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
