On 15/10/2025 20:16, James H. H. Lampert wrote:
On 10/15/25 11:07 AM, Olaf Kock wrote:
Security by Obscurity?
If all else fails . . .
As it stands, I've successfully renamed the manager context in my
guinea-pig server, and it continues to work. And certainly, if nothing
called manager exists, and there's no other way for an outsider without
terminal access to see what contexts *do* exist on the system, they'd
have to do an awful lot of trial-and-error.
But I've found enough information to start pursuing the JMX option.
I now have jmxterm installed and open on the box where the guinea-pig
server is running, and I've found and connected to the process in which
the JVM job for the Catalina job is running (which, because of the way
Java works on an IBM Midrange box, is not the Catalina job itself, but a
job called QP0ZSPWP).
Some other instructions a colleague found said to do:
bean Catalina:type=Context,host=localhost,name=/myapp
I tried that, with "test" (one of the running contexts):
bean Catalina:type=Context,host=localhost,name=/test
and I got:
#IllegalArgumentException: Please specify domain using either -d
option or domain command
That sounds like time to (1) ask for more help, and (2) eat my lunch.
I'd try commands like "domains" to list all the domains and "beans" to
list all the beans.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
