On 10/15/25 12:26 AM, Mark Thomas wrote:
It is brutal but if autoDeploy is enabled a quick and dirty way to do
that would be to move the manager directory out of the webapps directory
to stop it and move it back to start it.
Unfortunately, AutoDeploy in conf/server.xml is explicitly set to false,
because our webapp frequently requires certain parameters in its
WEB-INF/web.xml to be set manually, after the WAR file is expanded, but
before the webapp can do useful work. We found early-on (when we were
still running under Tomcat 7!) that with autoDeploy set to true, every
Tomcat restart would redeploy from the WAR file, wiping out those
parameter settings.
And we've already determined from long experience that certain things
that take effect without a Tomcat restart on any other platform require
a restart on IBM Midrange boxes. (We've always assumed that this was
because of something inherent to the IBM Midrange implementation of
Java, but for all I know, it could be the result of
unpackWARs="true" autoDeploy="false"
in conf/server.xml.
Just a thought: can manager be renamed, to something that neither a
hacker nor a security scan could easily guess, without command-line
access to the box, and still function?
--
JHHL
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
