Hi Andoni, I've got to manage tomcat in production with 99% availabilty, so I cannot afford a stop/start of Tomcat just to perform a minor update or bugfix. I want Tomcat in general run continuously.
So I have to avoid server.xml and its neighbourhood (/webapps/*.xml) where possible to achieve this goal. I think every application will have to achieve this goal at a certain point (=production level). I'd suggest to set up a "code of practice" , i.e. what has to be done to achieve high availability of Tomcat. My first suggestion at this point would be to deprecate the usage of server.xml for parameter storage and encourage e.g. environment-variables (env-entry) in web.xml of each Context. This makes parameter config reloadable using ant/the manager application. Does anybody know who could be in charge of this configuration issues and whom I could tell/discuss this idea with? I think this topic is going to be important for every production quality tomcat server out there, which has to run frequent updates of functionality (webapps). thx Johannes "Andoni" <[EMAIL PROTECTED]> 28.03.2003 13:36 Please respond to "Tomcat Users List" <[EMAIL PROTECTED]> To "Tomcat Users List" <[EMAIL PROTECTED]> cc Subject Re: Tomcat server.xml context-specific configuration I like putting everything possible into servlet.xml even though that means restarting tomcat. The advantage to me (and it is purely personal preference) is that then I can look at one file and see straight away everything that is going on with my system. I don't understand people who break up config files into smaller files here, there and everywhere around the tree. If you are just starting out and you are not used to configuring Tomcat servers then you might start this way and change if you don't like it or vice-versa. Hope that's of some help. Andoni. ----- Original Message ----- From: <[EMAIL PROTECTED]> To: "Tomcat Users List" <[EMAIL PROTECTED]> Sent: Friday, March 28, 2003 9:40 AM Subject: Tomcat server.xml context-specific configuration > Hi there, > > Since I got no replies to any of my inquiries regarding the use of > context-specific information in server.xml, it seems as if nobody else > uses this configuration property? > > What is the recommended place to put context-specific parameters into? > e.g. > <Context crossContext="true" debug="0" docBase="myapp" path="/myapp" > reloadable="true"> > <Logger className="org.apache.catalina.logger.FileLogger" > prefix="wartung_log." suffix=".txt" timestamp="true"/> > <ResourceLink name="jdbc/mydb" global="MyDatabase"/> > <Parameter name="myparam" override="false" value="xxx"/> > </Context> > > Should I > *) put it into server.xml (as is done with the examples demo-context) with > the disadvantage of having to restart Tomcat if changes occur. > *) put it into webapps/myapp.xml (with the same disadvantage as above) > *) put it into web.xml as servlet-specific configuration? > Or can I also store context-specific info in web.xml?? > > Thx alot > Johannes --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
