This is one reason I front all of our Tomcat servers with Apache+mod_jk. Adding a forced redirect or URL rewriting is trivial, and requires no changes to Tomcat or html files.
Tony Worthington | Sr. Technical Analyst | Kohl?s Department Stores N56 W17000 Ridgewood Drive | Menomonee Falls, WI 53051 | office: (262) 703-7763 | e-mail: tony.worthing...@kohls.com From: Tommy Morris <tommy.mor...@radioshack.com> To: arslist@ARSLIST.ORG Date: 11/04/2009 08:29 AM Subject: Re: Midtier login.jsp - caching... Sent by: "Action Request System discussion list(ARSList)" <arslist@ARSLIST.ORG> We have set in place a default.htm that acts as a redirect to the login page then deliver all of our links with the DNS server name as the address. If we have maintenance its is simple to just change the htm to a display a maintenance message instead of redirecting. Of course if users have the login page saved as a favorite or something similar that bypasses the default call then this solution will not work. -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Frank Caruso Sent: Tuesday, November 03, 2009 11:04 PM To: arslist@ARSLIST.ORG Subject: Re: Midtier login.jsp - caching... 1. Instead of blocking the login page you could just put the server in Administrator only mode while you performing your upgrades. 2. Restart your JSP engine after swapping in the new login.jsp. On Wed, Nov 4, 2009 at 3:11 AM, Shyam Attavar <atta...@sbcglobal.net> wrote: > ** > Dear Listers, > > We have a need to put a dummy JSP for our users during our maintenance > window, so that they are not logging into the server accidentally when we > are still in the process of making changes to the system. For this we are > planning to temporarily change the actual login.jsp to a dummy page > indicating the Maintenance Window message. > > However, just by swapping login.jsp does not necessarily take effect > immediately, until some significant time (in our case 60 minutes) has > elapsed from the time the page was changed to the next time the page was > accessed (by anyone). If someone logs in before that threshold has occurred, > we have to wait an additional 60 minutes. > > We can certainly force the update by deleting two files "login_jsp.java" and > "login_jsp.class" in the folder > <tomcat_install_dir>/work/Catalina/localhost/arsys/org/apache/jsp/shared and > then swapping the actual login.jsp with the dummy login.jsp. The next time > the login.jsp page is accessed, the two deleted files are automatically > recreated and after that users get the intended message. > > Although, this can probably work for the interim, we are hoping to have a > long term solution that is less intrusive. That arises a couple of questions > and if someone can shed some light on these, I would really appreciate it. > > 1) Why is it that, updating login.jsp does not take effect immediately and > what needs to be done for this to take effect immediately? > > 2) Looks like there is some sort of timeout threshold some where and I am > not sure what or where this is. Anyone know what to change and where to set > this threshold to a small number, so that updates to login.jsp take effect > immediately? > > We are using AR System 7.1.00 Patch 6 on Linux platform with Oracle 10g R3 > in the backend. > > Thanks, > -- > Shyam Attavar > _Platinum Sponsor: rmisoluti...@verizon.net ARSlist: "Where the Answers > Are"_ ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are" ********************************************************************** CONFIDENTIALITY NOTICE: This is a transmission from Kohl's Department Stores, Inc. and may contain information which is confidential and proprietary. If you are not the addressee, any disclosure, copying or distribution or use of the contents of this message is expressly prohibited. If you have received this transmission in error, please destroy it and notify us immediately at 262-703-7000. CAUTION: Internet and e-mail communications are Kohl's property and Kohl's reserves the right to retrieve and read any message created, sent and received. Kohl's reserves the right to monitor messages by authorized Kohl's Associates at any time without any further consent. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"
