If you want to avoid downtime then I agree with Andrew; you basically have to have a backup server. On the other hand, if all you want to do is present something more user-friendly than a 404 page, you could run Apache or some other web server in front of Tomcat and have Apache serve up an "out to lunch" page when you're doing a deployment.
- Isaac On Tue, Sep 15, 2009 at 3:33 AM, AndrewG <[email protected]> wrote: > > Alex, > > I think that if you have a single web server running - then it is > pretty much inevitable that there will be a (short) period of 'down > time' while a web app is installed and initialises. > > I know that this is not much help - but the obvious point that springs > to mind is that if your application is sufficiently important that it > being 'offline' for a short while inconveniences users greatly - then > there probably ought to be a 'fail over' server to pick up the load in > any case - otherwise if your only current server falls off its perch - > the users will be even more unhappy, and for rather longer. So I don't > think that any technical tricks you might come up with (a secondary > web server instance running on the same physical server, for example) > would involve a lot of fiddling about, and aren't really a solution. > > Andrew > > On Sep 15, 8:19 am, "alex.d" <[email protected]> wrote: >> Not quite. The problem is - while updating your application >> (undeploying it and deploying a new one) your website isn't working >> for severall minutes. And i would like to avoid this somehow. But the >> only thing that crosses my mind is having a second server and >> switching between them and i, sadly, don't have a second server. >> >> On 14 Sep., 16:39, Diego Lovison <[email protected]> wrote: >> >> > example.. when user type in >> > urlhttp://localhost:8080/youraplication/xxxx.html >> > xxxx.html dont exist in server.. will return "404 not fount" >> > you would like change for "this page dont exist in the server.. >> > please ........."? >> >> > On 14 set, 11:29, "alex.d" <[email protected]> wrote: >> >> > > The problem is: while undeploying old/deploying new version of >> > > application it's unavailable for severall minutes. Which is of course >> > > pretty annoying for the users. Is there any way to avoid this? I mean >> > > besides switching servers - i just have one :( > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
