Frank, We have multiple midtier instances that connect to a server group sitting behind a load balancer, out of which only one of the servers is the admin server. So, I am not sure if putting all the servers in Admin Only mode will work.
Also, with deleting the two files that I have mentioned in the original post, there is no need to restart the servlet engine (in our case - tomcat). Any other ideas? -- Shyam ________________________________ From: Frank Caruso <caruso.fr...@gmail.com> To: arslist@ARSLIST.ORG Sent: Tue, November 3, 2009 9:04:14 PM 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"
