On 10/20/25 9:42 AM, Christopher Schultz wrote:
There are documents, but it's easier to browse and read the descriptions if you connect using e.g. VisualVM and click through them. The documents are mbeans-descriptors.xml and they exist in each package, so there are many of them. If you browse via VisualVM (you can just run Tomcat locally on your desktop and browse them, which may be easier than trying to figure out how to connect to your running system), all those files are collated and presented via a GUI.
I managed to get VisualVM and a Tomcat server running on my desktop Mac, and talking to each other, and (thanks Mr. Caldarale) add the mbeans plug-in. I can find an operation for testing an address against the RemoteAddrValve's "allow" attribute, but not for changing it.
Back to the IP address. Instead of changing RemoteIPValve from allowing 127.0.0.1 to allowing "anybody" (or whatever), why not just change it to allow any connection from the controlling machine (where you can connect via JMX)?
If I could do that with the "problem" box, I wouldn't be in this mess (and wouldn't need JMX, or JMXterm, or VisualVM), because it would then be just like every other installation. Unfortunately, there's the small issue that they've got this insane firewall setup in which Tomcat sees *all* outside traffic as coming from (I'm guessing) the firewall's address. Makes me want to (as George Washington really did put it, in January of 1776) retire to the back-country, and live in a wigwam.
-- JHHL --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
