In response to
Either I'm stopping and restarting the wrong bean, or stopping and
restarting the bean doesn't reload the context.xml.
I'll try other beans, but if anybody can suggest a different bean to
try, please do.
On 10/16/25 10:08 AM, Christopher Schultz wrote:
Exactly which file did you change?
Dear Mr. Schultz:
The object here is to be able to have the manager context unreachable
from the outside by default, but make it reachable as needed, without
having to restart Tomcat in order to do it. (Running manager from the
box itself is not possible, because it's an IBM Midrange box.)
AutoDeploy is set to false in conf/server.xml, because otherwise, WAR
files get re-expanded, overwriting any instances of our webapp that have
had internal parameters set in their own web.xml files.
So I tried stopping manager (from a jmxterm session running on the same
box), changing the RemoteAddrValve in the manager context's
META-INF/context.xml file, and then starting manager back up. No joy.
The change had no effect whatsoever, whether I changed the allow clause,
or I commented/uncommented the filter.
I also tried starting Tomcat with the manager context physically absent,
then moving it in while Tomcat was running, but JMX couldn't find the
beans for it. Ditto if I tried hiding manager with an ignoreDeploy
clause on the host tag in conf/server.xml.
So far, the only thing I've found that works is renaming manager to
something that would be difficult to guess, which is merely "security by
obscurity" (then again, so are passwords, PINs, and combination locks).
This summarizes everything I know so far.
--
JHHL
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
