Operational issues are always highly specific to the environment you're running on, unfortunately. There's always the old favorite "Scheduled Downtime" where you tell people when the application will be offline for maintenance.
> -----Original Message----- > From: Taavi Tiirik [mailto:[EMAIL PROTECTED] > Sent: Friday, August 13, 2004 9:53 AM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: Re: [OS-webwork] webwork, maverick and 24x7 > > > > Thank you all so far for these thoughs. Additional node > and load balancer would be good solution of course > and is definitely the right way to go. > > The only problem is that there is not too much load > to balance :) > > I now feel that our users can live with the fact that the > site is down for five minutes or so. But there is a lot of > time consuming "filling in data input forms" going on > in these applications. So I have to make sure that if > I stop a webapp (the container itself remains running) > then the application in root context will take over, > persist all the form data and give an easy to > understand explanation of what is going on. And once > the new version of the webapp is deployed and is up > and running again the user should be able to continue > like nothing evere happened. > > This is just an idea and I dont know if this kind of > solution is reliable. And would it work with different > containers? With Tomcat it kind of works. The only worrying > thing is that if I hit reload button heavily duering the > startup of webapp then I have seen error messages. > > So it all depends on an implementation of a container > and this can make things very vulnerable. > > taavi > > ----- Original Message ----- > From: "Rickard Öberg" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]> > Sent: Friday, August 13, 2004 4:09 PM > Subject: Re: [OS-webwork] webwork, maverick and 24x7 > > > > Taavi Tiirik wrote: > > > I have two webapps using Webwork, Maverick, Tomcat 4.1, > Hibernate, > > > JSP views (but switching to freemarker soon). > > > > > > These web applications have to be available 7 days a > week, 24 hours > > > a day but the problem is they need new features almoust > every day. > > > But I am kind of tired of deploying new releases duering > night when > > > there is less users. > > > > > > So I am trying to find a best way how to deploy changes > into working > > > system. If this is possible at all. > > > > > > Please be so kind and share your experiences. > > > > Yeah, we have the same problem and currently we try to find > low-usage > > hours to do it. We'll be looking more at the 2-node cluster > strategy > > Jason mentioned in the future. > > > > If you have the luxury of having static output you could always > > generate the HTML and shove them onto an Apache server. > Then you can > > upgrade the dynamic stuff behind the covers. > > > > /Rickard > > > > > > > --------------------------------------------------------------------- > > 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] > > ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 [INVALID FOOTER]
