I’m guessing that the OP’s configuration or user permissions are not allowing war unpacking to update the webapps directory to the new version of the webapps.
This has happened to me on some of my installations in the past when an admin starts as root vs. a special user like tomcat. This is often due to VM startup of Tomcat vs. restart script as a user. For example: If I originally deploy myapp.war as tomcat user but Tomcat is running as root it will create the myapp directory next to it with root ownership. Now I restart Tomcat and it is running as tomcat user. I replace myapp.war and Tomcat does not have permission to replace the old version owned by root. Without the OP providing configuration details it is difficult to know, but this is what I have found. Regards, Dave > On Mar 5, 2018, at 1:30 PM, Leon Rosenberg <rosenberg.l...@gmail.com> wrote: > > Hello, > > can you explain what you mean by 'caching' ? > > regards > Leon > > On Mon, Mar 5, 2018 at 10:26 PM, Kenneth Taylor < > kenneth.tay...@dataexpress.com> wrote: > >> We are having a serious problem with Tomcat (8.5). Twice it has decided >> to PERMANENTLY cache one of our webapps. We are unable to update that >> webapp. We’ve tried everything imaginable, short of uninstalling Tomcat, >> which is the next step. >> >> >> >> Where is this cache and how do we turn it off? >> >> >> >> Why in the world would anyone want Tomcat to work this way? This is a >> fatal flaw worthy of a Darwin Award. >> >> >> >> Frustrated. >> >> >> >> Ken >> >> >> >> Disclaimer: This email from DMBGroup LLC, DMB Consulting Services LLC, or >> the personnel associated with either entity (collectively "*DMB*") and >> attachments, contain *CONFIDENTIAL, PRIVILEGED AND PROPRIETARY *information >> for exclusive use of the addressee individual(s) or entity. Unauthorized >> viewing, copying, disclosure, distribution or use of this e-mail or >> attachments may be subject to legal restriction or sanction. If received in >> error, notify sender immediately by return e-mail and delete original >> message and attachments. Nothing contained in this e-mail or attachments >> shall satisfy the requirements for a writing unless specifically stated. >> Nothing contained herein shall constitute a contract or electronic >> signature under the Electronic Signatures in Global and National Commerce >> Act, any version of the Uniform Electronic Transactions Act or any other >> statute governing electronic transactions. Opinions and statements >> expressed in this e-mail and any attachments are those of the individual >> sender and not necessarily of DMB. DMB does not guarantee this e-mail >> transmission is secured, error or virus-free. Neither DMB nor the sender of >> this e-mail accepts liability for errors or omissions in the contents of >> this e-mail, which arise as a result of e-mail transmission. . >>
signature.asc
Description: Message signed with OpenPGP
