I'm not even concerned with the webapp being automatically reloadable. I can reload from the manager or just bounce tomcat. Mentioning WatchedResource is a red herring.
If I war a webapp with many class files in various packages in WEB-INF/classes with reloadable=false and unpackwars=false it will take over a minute to start the server. If I war a webapp with only my servlet class in WEB-INF/classes and place the dependent class files in a jar and put that jar in WEB-INF/lib with reloadable=false and unpackwars=false then it only takes a few seconds for the server to start. Not to mention on a less powerful windows xp machine the first scenario starts in seconds... -----Original Message----- From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED] Sent: Friday, August 24, 2007 2:39 PM To: Tomcat Users List Subject: Re: Tomcat6, apache2, mod_jk, non-APR, windows 2000, slow server startup with unpacked WAR Dan Beaulieu wrote: > Well I guess this gets into the nuances of classloaders that I am completely > unfamiliar with, but I wonder why it would be any different if those few > thousand classes are now packed in a jar and made available as a library to > the webapp? > nothing to do with classloading, all to do with "resource monitoring", as you set reloadable="true" but by now, you should have changed that to reloadable="false" and control what gets monitored using the WatchedResource element in your context config instead Filip > We run our standalone appserver from a jar, and loading is instantaneous, > and it has even more classes than the webapp does, from my point of view, it > should be no different. > > -----Original Message----- > From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED] > Sent: Friday, August 24, 2007 10:42 AM > To: Tomcat Users List > Subject: Re: Tomcat6, apache2, mod_jk, non-APR, windows 2000, slow server > startup with unpacked WAR > > Dan Beaulieu wrote: > >> Right, I understand the function of the reloadable attribute. What I don't >> understand is how on a modern computer, registering 2000 locations in >> memory/on disk to check for changes could take over a minute. Imagine just >> what it is doing, it isn't even checking for changes yet, its just >> registering the classes to check for changes. >> >> > you have unpackWARs="false", that means that it has to unzip/extract > 2000 files in memory from your .war file, one by one > > Filip > >> Not to mention, it doesn't really make sense when using an unpackable war. >> >> -----Original Message----- >> From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED] >> Sent: Thursday, August 23, 2007 5:25 PM >> To: Tomcat Users List >> Subject: Re: Tomcat6, apache2, mod_jk, non-APR, windows 2000, slow server >> startup with unpacked WAR >> >> even then, you should set reloadable="false" >> the flag name is misleading, all apps are reloadable, regardless of what >> that setting is (basically autoDeploy="true" -> webapps are reloadable) >> >> read up on the reloadable flag, you'll see that it actually would add >> all 2000 files to be monitored by tomcat, and could have noticeable impact >> >> Filip >> >> Dan Beaulieu wrote: >> >> >>> Reloadable is true, and unpack is false. >>> >>> If we tell it to unpack it'll take a long time to start up, but then >>> subsequent start ups with out deleting the webapp dir are fast. >>> >>> Agreed, reloadable shouldn't have that much of an impact. >>> >>> -----Original Message----- >>> From: Len Popp [mailto:[EMAIL PROTECTED] >>> Sent: Thursday, August 23, 2007 2:43 PM >>> To: Tomcat Users List >>> Subject: Re: Tomcat6, apache2, mod_jk, non-APR, windows 2000, slow server >>> startup with unpacked WAR >>> >>> Is it unpacking the war during startup? Unzipping 2000 files takes a >>> while (even if they're small). >>> >>> >>> >> >> >> --------------------------------------------------------------------- >> To start a new topic, e-mail: users@tomcat.apache.org >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> --------------------------------------------------------------------- >> To start a new topic, e-mail: users@tomcat.apache.org >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> >> >> > > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
