On 10/20/25 9:42 AM, Christopher Schultz wrote:
So there is the file in
CATALINA_HOME/webapps/yourapp/META-INF/context.xml but that file gets
copied into CATALINA_HOME/conf/Catalina/localhost/yourapp.xml when your
application is deployed, if it doesn't already exist. If the application
is re-deployed (without being undeployed), that file IS NOT UPDATED. And
this file is preferred by Tomcat, so it won't load the file you have in
bundled with your application.
Curiouser and curiouser:
I just double-checked that CATALINA_HOME is what I expect it to be (it
is), and I used two different routes to check the context of
conf/Catalina/localhost.
conf/Catalina/localhost is completely empty.
Tomcat (9.0.110) is running. Our webapps are presenting a sign-on page.
The renamed manager webapp is presenting a sign-on pop-up, and when that
is satisfied, a typical Manager screen (and normally, we use Manager
only for uploading updates, and for gathering troubleshooting data).
And yet conf/Catalina/localhost is completely empty.
I've just looked at the Tomcat on the cloud Linux box where our web
sites live. It's got two directories called "Catalina":
./etc/tomcat/Catalina
./var/cache/tomcat/work/Catalina
/etc/tomcat/Catalina/localhost is just as empty as its counterpart on
the guinea-pig, but /var/cache/tomcat/work/Catalina/localhost has
subdirectories corresponding to the webapp contexts.
--
JHHL
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
