On the other hand you could disable on the fly compiling and hence checking for updates (tomcat checks if the jsp page has been changed and if there is a need to recompile it). Disabling this can get you some performance boost and reduce io. Of course it only matters if you really have traffic.
leon On 8/7/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Hi Leon, > > If the jsp gets compiled once after the war files get deployed then I would > be willing for the server to be a bit less responsive for the 2 minutes or > so that it takes for the application to deploy. > > Assuming that you would deploy by copying files, copying one war file for me > is simpler then copying a directory or larger collection of files. > > Regards > > > -----Original Message----- > > From: Leon Rosenberg [mailto:[EMAIL PROTECTED] > > Sent: 07 August 2007 10:58 > > To: Tomcat Users List > > Subject: Re: Best practice application deployement > > > > I concluded that from statements from Remy on different > > occasions; Jason Brittain also mentions it in his new book, > > and finally our production experience tells us that its > > better to. Unless you want your server to be busy compiling > > jsps instead of serving requests some time after start :-) > > > > regards > > Leon > > > ______________________________________________________________________ > This email has been scanned by the MessageLabs Email Security System. > For more information please visit http://www.messagelabs.com/email > ______________________________________________________________________ --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
