Yes, you are right, it's confusing the way I said it. What I meant was : one web context that contains a lot of custom class-files.
Normally, I would agree with you that each application should have it's own context, but there are some reasons why this approach isn't taken : 1) the system we work with expects only one specific web context to be used 2) every application uses common functionality + configuration setup anyway (e.g. database config) 3) I'm talking about hundred's of mostly small applications, imho confuring a separate web context for each would be overkill. Of course, the advantage of having a separate context for each app would be the total non-intrusion when reloading a specific context :s -----Original Message----- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: 07 September 2004 15:10 To: Tomcat Users List Subject: RE: is reloading the web context sufficient ? Hi, In the Tomcat world, one web application = one web context. So please clarify what you mean by "a lot of applications (in one web context)". Yoav Shapira Millennium Research Informatics >-----Original Message----- >From: Quinten Verheyen [mailto:[EMAIL PROTECTED] >Sent: Tuesday, September 07, 2004 6:15 AM >To: Tomcat Users List >Subject: is reloading the web context sufficient ? > >Hi, > >I'm wondering about strategies for having a production (Tomcat) webserver >that hosts a lot of applications (in one web context) and needs to be >running 24/7. The main issue is not to lose any traffic coming in/out. > >Is reloading a web context via the manager app for every change made to >class-files, lib's etc. a good option ? I mean, does this have any >implications on internet traffic getting lost at the moment the reload >occurs ? >The same reasoning would apply for deploying/undeploying through the admin >webapp. >My guess is that the safe way is handling this through clustering (DNS >round robin), and having 2 tomcat containers running with the same web >context, but only one of them would be accessed at a time. > >Fill me in if I'm wrong. > >Quinten > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
