Re: How to do Downtime with a Apache/Tomcat webapp
I had a similar requirement in my app... We had a two-hour window per day when the app was unavailable because background tasks were processing. The server was still up, and so was the app technically, but it was not available. I wrote a filter to take care of this. I had a flag in application context to tell if the app was up or not too, so that if I had to make the app unavailable during a time when it normally was available, I just set the flag. I also defined a single user that was still allowed to get in (another context parameter). This works out great. -- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com Len Popp wrote: I've been thinking about the same problem, but I haven't gotten around to working on it seriously. How about this: Instead of fiddling with the JkMount directives in Apache, swap the web.xml in your Tomcat app so it points to a minimal servlet that returns the Out of service page for all requests. Does that sound like it would work? It would be less disruptive because you don't have to restart Apache (if there's more to the web site than the one Tomcat app). Plus this will work with stand-alone Tomcat. On 5/15/05, Richard Mixon (qwest) [EMAIL PROTECTED] wrote: I'm curious how folks handle letting users know that their webapp is down when doing maintenance. We've got a pretty standard setup. Our informational/static site is served by Apache 2.0.x. We use mod_jk to link to a page in our webapplications, triggering CMA for authentication and login. We run Tomcat 5.5.x. Although we actually have Tomcat clustered, there are still times when we need to make the application unavailable. (i.e. doing database schema changes, etc.). I would like for a page to be displayed that says the application is temporarily not available. So, what's the best way to do this? One way I can think of is to modify the JkMount directives so that may context name was not mapped to Tomcat, but instead to a static page - the just do a restart. Trouble is some of our users have bookmarks into various pages/actions in the application - we would somehow have to mapp all pages that began with the context name to this single page. This sounds a bit messy. Is there a more straightforward way of doing this? Thank you - Richard - 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]
Re: How to do Downtime with a Apache/Tomcat webapp
I believe this link has the info you are looking for. It discusses displaying error messages by Apache when the app server is down. http://wiki.apache.org/cocoon/ApacheModProxy Ed On Mon, 2005-05-16 at 11:33 -0400, Len Popp wrote: I've been thinking about the same problem, but I haven't gotten around to working on it seriously. How about this: Instead of fiddling with the JkMount directives in Apache, swap the web.xml in your Tomcat app so it points to a minimal servlet that returns the Out of service page for all requests. Does that sound like it would work? It would be less disruptive because you don't have to restart Apache (if there's more to the web site than the one Tomcat app). Plus this will work with stand-alone Tomcat. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to do Downtime with a Apache/Tomcat webapp
Len, Sounds simple - but maybe I'm missing something. How do I do maintenance on the site context (under webapp) if the context is being used to show this simple page? It may end up being simplest to alter (or swap in) the Apache config file and do a reload. On my site the reload is pretty quick and I do not think it disrupts active Tomcat sessions (in other contexts). Thanks - Richard -Original Message- From: Len Popp [mailto:[EMAIL PROTECTED] Sent: Monday, May 16, 2005 8:33 AM To: Tomcat Users List Subject: Re: How to do Downtime with a Apache/Tomcat webapp I've been thinking about the same problem, but I haven't gotten around to working on it seriously. How about this: Instead of fiddling with the JkMount directives in Apache, swap the web.xml in your Tomcat app so it points to a minimal servlet that returns the Out of service page for all requests. Does that sound like it would work? It would be less disruptive because you don't have to restart Apache (if there's more to the web site than the one Tomcat app). Plus this will work with stand-alone Tomcat. On 5/15/05, Richard Mixon (qwest) [EMAIL PROTECTED] wrote: I'm curious how folks handle letting users know that their webapp is down when doing maintenance. We've got a pretty standard setup. Our informational/static site is served by Apache 2.0.x. We use mod_jk to link to a page in our webapplications, triggering CMA for authentication and login. We run Tomcat 5.5.x. Although we actually have Tomcat clustered, there are still times when we need to make the application unavailable. (i.e. doing database schema changes, etc.). I would like for a page to be displayed that says the application is temporarily not available. So, what's the best way to do this? One way I can think of is to modify the JkMount directives so that may context name was not mapped to Tomcat, but instead to a static page - the just do a restart. Trouble is some of our users have bookmarks into various pages/actions in the application - we would somehow have to mapp all pages that began with the context name to this single page. This sounds a bit messy. Is there a more straightforward way of doing this? Thank you - Richard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Len Popp - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to do Downtime with a Apache/Tomcat webapp
Len, Sounds simple - but maybe I'm missing something. How do I do maintenance on the site context (under webapp) if the context is being used to show this simple page? It may end up being simplest to alter (or swap in) the Apache config file and do a reload. On my site the reload is pretty quick and I do not think it disrupts active Tomcat sessions (in other contexts). Thanks - Richard -Original Message- From: Len Popp [mailto:[EMAIL PROTECTED] Sent: Monday, May 16, 2005 8:33 AM To: Tomcat Users List Subject: Re: How to do Downtime with a Apache/Tomcat webapp I've been thinking about the same problem, but I haven't gotten around to working on it seriously. How about this: Instead of fiddling with the JkMount directives in Apache, swap the web.xml in your Tomcat app so it points to a minimal servlet that returns the Out of service page for all requests. Does that sound like it would work? It would be less disruptive because you don't have to restart Apache (if there's more to the web site than the one Tomcat app). Plus this will work with stand-alone Tomcat. On 5/15/05, Richard Mixon (qwest) [EMAIL PROTECTED] wrote: I'm curious how folks handle letting users know that their webapp is down when doing maintenance. We've got a pretty standard setup. Our informational/static site is served by Apache 2.0.x. We use mod_jk to link to a page in our webapplications, triggering CMA for authentication and login. We run Tomcat 5.5.x. Although we actually have Tomcat clustered, there are still times when we need to make the application unavailable. (i.e. doing database schema changes, etc.). I would like for a page to be displayed that says the application is temporarily not available. So, what's the best way to do this? One way I can think of is to modify the JkMount directives so that may context name was not mapped to Tomcat, but instead to a static page - the just do a restart. Trouble is some of our users have bookmarks into various pages/actions in the application - we would somehow have to mapp all pages that began with the context name to this single page. This sounds a bit messy. Is there a more straightforward way of doing this? Thank you - Richard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Len Popp - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to do Downtime with a Apache/Tomcat webapp
From: Richard Mixon (qwest) [EMAIL PROTECTED] Sent: Sunday, May 15, 2005 8:57 PM I'm curious how folks handle letting users know that their webapp is down when doing maintenance. We have an alternate httpd.conf file for Apache that is configured to send everybody to site down come back later static site, then we simply bounce Apache with the new config. It's is not particularly subtle, but we're not a 24x7 site so much, and it's more to let folks coming in know what's happening. But it's simple and quick. Regards, Will Hartung ([EMAIL PROTECTED]) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to do Downtime with a Apache/Tomcat webapp
Will, Thanks - that may be the simplest solution. It just seems errors prone (i.e. updating one of the httpd.conf files, but not the other). Still its appealing for my situation. I am going to better check out the reference Ed sent in an earlier post - that seems to have some potential. - Richard -Original Message- From: Will Hartung [mailto:[EMAIL PROTECTED] Sent: Monday, May 16, 2005 4:43 PM To: Tomcat Users List Subject: Re: How to do Downtime with a Apache/Tomcat webapp From: Richard Mixon (qwest) [EMAIL PROTECTED] Sent: Sunday, May 15, 2005 8:57 PM I'm curious how folks handle letting users know that their webapp is down when doing maintenance. We have an alternate httpd.conf file for Apache that is configured to send everybody to site down come back later static site, then we simply bounce Apache with the new config. It's is not particularly subtle, but we're not a 24x7 site so much, and it's more to let folks coming in know what's happening. But it's simple and quick. Regards, Will Hartung ([EMAIL PROTECTED]) - 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]
RE: How to do Downtime with a Apache/Tomcat webapp
Will, Thanks - that may be the simplest solution. It just seems errors prone (i.e. updating one of the httpd.conf files, but not the other). Still its appealing for my situation. I am going to better check out the reference Ed sent in an earlier post - that seems to have some potential. - Richard -Original Message- From: Will Hartung [mailto:[EMAIL PROTECTED] Sent: Monday, May 16, 2005 4:43 PM To: Tomcat Users List Subject: Re: How to do Downtime with a Apache/Tomcat webapp From: Richard Mixon (qwest) [EMAIL PROTECTED] Sent: Sunday, May 15, 2005 8:57 PM I'm curious how folks handle letting users know that their webapp is down when doing maintenance. We have an alternate httpd.conf file for Apache that is configured to send everybody to site down come back later static site, then we simply bounce Apache with the new config. It's is not particularly subtle, but we're not a 24x7 site so much, and it's more to let folks coming in know what's happening. But it's simple and quick. Regards, Will Hartung ([EMAIL PROTECTED]) - 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]
RE: How to do Downtime with a Apache/Tomcat webapp
Filters work great for this. Also, if you have a cluster, you probably have a load balancer in front of the cluster. If you do, then you could have the load balancer direct all your traffic to a server that runs Apache and only served up a 'Sorry the site is down' page. When the site is back up you can redirect the traffic back to the servers. This will allow you to do maintenance on the DB, Application, Tomcat etc. Subir -Original Message- From: Frank W. Zammetti [mailto:[EMAIL PROTECTED] Sent: Monday, May 16, 2005 12:36 PM To: Tomcat Users List Subject: Re: How to do Downtime with a Apache/Tomcat webapp I had a similar requirement in my app... We had a two-hour window per day when the app was unavailable because background tasks were processing. The server was still up, and so was the app technically, but it was not available. I wrote a filter to take care of this. I had a flag in application context to tell if the app was up or not too, so that if I had to make the app unavailable during a time when it normally was available, I just set the flag. I also defined a single user that was still allowed to get in (another context parameter). This works out great. -- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com Len Popp wrote: I've been thinking about the same problem, but I haven't gotten around to working on it seriously. How about this: Instead of fiddling with the JkMount directives in Apache, swap the web.xml in your Tomcat app so it points to a minimal servlet that returns the Out of service page for all requests. Does that sound like it would work? It would be less disruptive because you don't have to restart Apache (if there's more to the web site than the one Tomcat app). Plus this will work with stand-alone Tomcat. On 5/15/05, Richard Mixon (qwest) [EMAIL PROTECTED] wrote: I'm curious how folks handle letting users know that their webapp is down when doing maintenance. We've got a pretty standard setup. Our informational/static site is served by Apache 2.0.x. We use mod_jk to link to a page in our webapplications, triggering CMA for authentication and login. We run Tomcat 5.5.x. Although we actually have Tomcat clustered, there are still times when we need to make the application unavailable. (i.e. doing database schema changes, etc.). I would like for a page to be displayed that says the application is temporarily not available. So, what's the best way to do this? One way I can think of is to modify the JkMount directives so that may context name was not mapped to Tomcat, but instead to a static page - the just do a restart. Trouble is some of our users have bookmarks into various pages/actions in the application - we would somehow have to mapp all pages that began with the context name to this single page. This sounds a bit messy. Is there a more straightforward way of doing this? Thank you - Richard - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to do Downtime with a Apache/Tomcat webapp
From: Richard Mixon (qwest) [EMAIL PROTECTED] Sent: Tuesday, May 17, 2005 7:53 AM Will, Thanks - that may be the simplest solution. It just seems errors prone (i.e. updating one of the httpd.conf files, but not the other). Still its appealing for my situation. I am going to better check out the reference Ed sent in an earlier post - that seems to have some potential. To be clear, you don't update the httpd.conf file, rather you have two versions (up version and down version), then you simply restart Apache with the correct version as appropriate. Regards, Will Hartung ([EMAIL PROTECTED]) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to do Downtime with a Apache/Tomcat webapp
Frank, Thanks - that's a neat feature to add. It does not work for my current requirement (the entire webapp is down at the time), but there are definite times when I want the webapp up and only limited access (e.g. checking out a just installed/upgraded application). - Richard -Original Message- From: Frank W. Zammetti [mailto:[EMAIL PROTECTED] Sent: Monday, May 16, 2005 12:36 PM To: Tomcat Users List Subject: Re: How to do Downtime with a Apache/Tomcat webapp I had a similar requirement in my app... We had a two-hour window per day when the app was unavailable because background tasks were processing. The server was still up, and so was the app technically, but it was not available. I wrote a filter to take care of this. I had a flag in application context to tell if the app was up or not too, so that if I had to make the app unavailable during a time when it normally was available, I just set the flag. I also defined a single user that was still allowed to get in (another context parameter). This works out great. -- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com Len Popp wrote: I've been thinking about the same problem, but I haven't gotten around to working on it seriously. How about this: Instead of fiddling with the JkMount directives in Apache, swap the web.xml in your Tomcat app so it points to a minimal servlet that returns the Out of service page for all requests. Does that sound like it would work? It would be less disruptive because you don't have to restart Apache (if there's more to the web site than the one Tomcat app). Plus this will work with stand-alone Tomcat. On 5/15/05, Richard Mixon (qwest) [EMAIL PROTECTED] wrote: I'm curious how folks handle letting users know that their webapp is down when doing maintenance. We've got a pretty standard setup. Our informational/static site is served by Apache 2.0.x. We use mod_jk to link to a page in our webapplications, triggering CMA for authentication and login. We run Tomcat 5.5.x. Although we actually have Tomcat clustered, there are still times when we need to make the application unavailable. (i.e. doing database schema changes, etc.). I would like for a page to be displayed that says the application is temporarily not available. So, what's the best way to do this? One way I can think of is to modify the JkMount directives so that may context name was not mapped to Tomcat, but instead to a static page - the just do a restart. Trouble is some of our users have bookmarks into various pages/actions in the application - we would somehow have to mapp all pages that began with the context name to this single page. This sounds a bit messy. Is there a more straightforward way of doing this? Thank you - Richard - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to do Downtime with a Apache/Tomcat webapp
Frank, Thanks - that's a neat feature to add. It does not work for my current requirement (the entire webapp is down at the time), but there are definite times when I want the webapp up and only limited access (e.g. checking out a just installed/upgraded application). - Richard -Original Message- From: Frank W. Zammetti [mailto:[EMAIL PROTECTED] Sent: Monday, May 16, 2005 12:36 PM To: Tomcat Users List Subject: Re: How to do Downtime with a Apache/Tomcat webapp I had a similar requirement in my app... We had a two-hour window per day when the app was unavailable because background tasks were processing. The server was still up, and so was the app technically, but it was not available. I wrote a filter to take care of this. I had a flag in application context to tell if the app was up or not too, so that if I had to make the app unavailable during a time when it normally was available, I just set the flag. I also defined a single user that was still allowed to get in (another context parameter). This works out great. -- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com Len Popp wrote: I've been thinking about the same problem, but I haven't gotten around to working on it seriously. How about this: Instead of fiddling with the JkMount directives in Apache, swap the web.xml in your Tomcat app so it points to a minimal servlet that returns the Out of service page for all requests. Does that sound like it would work? It would be less disruptive because you don't have to restart Apache (if there's more to the web site than the one Tomcat app). Plus this will work with stand-alone Tomcat. On 5/15/05, Richard Mixon (qwest) [EMAIL PROTECTED] wrote: I'm curious how folks handle letting users know that their webapp is down when doing maintenance. We've got a pretty standard setup. Our informational/static site is served by Apache 2.0.x. We use mod_jk to link to a page in our webapplications, triggering CMA for authentication and login. We run Tomcat 5.5.x. Although we actually have Tomcat clustered, there are still times when we need to make the application unavailable. (i.e. doing database schema changes, etc.). I would like for a page to be displayed that says the application is temporarily not available. So, what's the best way to do this? One way I can think of is to modify the JkMount directives so that may context name was not mapped to Tomcat, but instead to a static page - the just do a restart. Trouble is some of our users have bookmarks into various pages/actions in the application - we would somehow have to mapp all pages that began with the context name to this single page. This sounds a bit messy. Is there a more straightforward way of doing this? Thank you - Richard - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to do Downtime with a Apache/Tomcat webapp
Ed, Thank you - a very cool reference with a number of tricks/knowledge. - Richard -Original Message- From: Gmail User [mailto:[EMAIL PROTECTED] Sent: Monday, May 16, 2005 1:23 PM To: Tomcat Users List Subject: Re: How to do Downtime with a Apache/Tomcat webapp I believe this link has the info you are looking for. It discusses displaying error messages by Apache when the app server is down. http://wiki.apache.org/cocoon/ApacheModProxy Ed On Mon, 2005-05-16 at 11:33 -0400, Len Popp wrote: I've been thinking about the same problem, but I haven't gotten around to working on it seriously. How about this: Instead of fiddling with the JkMount directives in Apache, swap the web.xml in your Tomcat app so it points to a minimal servlet that returns the Out of service page for all requests. Does that sound like it would work? It would be less disruptive because you don't have to restart Apache (if there's more to the web site than the one Tomcat app). Plus this will work with stand-alone Tomcat. - 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]
RE: How to do Downtime with a Apache/Tomcat webapp
Ed, Thank you - a very cool reference with a number of tricks/knowledge. - Richard -Original Message- From: Gmail User [mailto:[EMAIL PROTECTED] Sent: Monday, May 16, 2005 1:23 PM To: Tomcat Users List Subject: Re: How to do Downtime with a Apache/Tomcat webapp I believe this link has the info you are looking for. It discusses displaying error messages by Apache when the app server is down. http://wiki.apache.org/cocoon/ApacheModProxy Ed On Mon, 2005-05-16 at 11:33 -0400, Len Popp wrote: I've been thinking about the same problem, but I haven't gotten around to working on it seriously. How about this: Instead of fiddling with the JkMount directives in Apache, swap the web.xml in your Tomcat app so it points to a minimal servlet that returns the Out of service page for all requests. Does that sound like it would work? It would be less disruptive because you don't have to restart Apache (if there's more to the web site than the one Tomcat app). Plus this will work with stand-alone Tomcat. - 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]
Re: How to do Downtime with a Apache/Tomcat webapp
Hey, maybe *I'm* missing something. :-) I haven't tried this yet. I guess it only works if the web app is unpacked, not in a war file. (That's how my site is currently.) When the site is down it's running a minimal web app that is only using two files - web.xml and the jsp or servlet that's returning the site-down page. All other files and the database are not in use and can be munged at will. The original question mentioned database maintenance in particular. In that case it doesn't really matter what the web app is doing, as long as it's not accessing the database. The idea of using a filter to turn off the app sounds good for this. On 5/16/05, Richard Mixon (qwest) [EMAIL PROTECTED] wrote: Len, Sounds simple - but maybe I'm missing something. How do I do maintenance on the site context (under webapp) if the context is being used to show this simple page? It may end up being simplest to alter (or swap in) the Apache config file and do a reload. On my site the reload is pretty quick and I do not think it disrupts active Tomcat sessions (in other contexts). Thanks - Richard -Original Message- From: Len Popp [mailto:[EMAIL PROTECTED] Sent: Monday, May 16, 2005 8:33 AM To: Tomcat Users List Subject: Re: How to do Downtime with a Apache/Tomcat webapp I've been thinking about the same problem, but I haven't gotten around to working on it seriously. How about this: Instead of fiddling with the JkMount directives in Apache, swap the web.xml in your Tomcat app so it points to a minimal servlet that returns the Out of service page for all requests. Does that sound like it would work? It would be less disruptive because you don't have to restart Apache (if there's more to the web site than the one Tomcat app). Plus this will work with stand-alone Tomcat. On 5/15/05, Richard Mixon (qwest) [EMAIL PROTECTED] wrote: I'm curious how folks handle letting users know that their webapp is down when doing maintenance. We've got a pretty standard setup. Our informational/static site is served by Apache 2.0.x. We use mod_jk to link to a page in our webapplications, triggering CMA for authentication and login. We run Tomcat 5.5.x. Although we actually have Tomcat clustered, there are still times when we need to make the application unavailable. (i.e. doing database schema changes, etc.). I would like for a page to be displayed that says the application is temporarily not available. So, what's the best way to do this? One way I can think of is to modify the JkMount directives so that may context name was not mapped to Tomcat, but instead to a static page - the just do a restart. Trouble is some of our users have bookmarks into various pages/actions in the application - we would somehow have to mapp all pages that began with the context name to this single page. This sounds a bit messy. Is there a more straightforward way of doing this? Thank you - Richard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Len Popp - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to do Downtime with a Apache/Tomcat webapp
I've been thinking about the same problem, but I haven't gotten around to working on it seriously. How about this: Instead of fiddling with the JkMount directives in Apache, swap the web.xml in your Tomcat app so it points to a minimal servlet that returns the Out of service page for all requests. Does that sound like it would work? It would be less disruptive because you don't have to restart Apache (if there's more to the web site than the one Tomcat app). Plus this will work with stand-alone Tomcat. On 5/15/05, Richard Mixon (qwest) [EMAIL PROTECTED] wrote: I'm curious how folks handle letting users know that their webapp is down when doing maintenance. We've got a pretty standard setup. Our informational/static site is served by Apache 2.0.x. We use mod_jk to link to a page in our webapplications, triggering CMA for authentication and login. We run Tomcat 5.5.x. Although we actually have Tomcat clustered, there are still times when we need to make the application unavailable. (i.e. doing database schema changes, etc.). I would like for a page to be displayed that says the application is temporarily not available. So, what's the best way to do this? One way I can think of is to modify the JkMount directives so that may context name was not mapped to Tomcat, but instead to a static page - the just do a restart. Trouble is some of our users have bookmarks into various pages/actions in the application - we would somehow have to mapp all pages that began with the context name to this single page. This sounds a bit messy. Is there a more straightforward way of doing this? Thank you - Richard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Len Popp
