Hey Joe,
currently the default java 5 jmx rmi implementation can't set a fix rmi
port.
You can only set the naming port. Really bad, but the only way to change
this,
is to implement a tomcat listener and start your own rmi connector. I am
very happy
to see the implementation. :-)
Peter
Joe R. Lindsay schrieb:
So, I have it up and running, but it seems that remote
monitoring requires a random 2nd data port
So, even when I set the remote jmx port to say 1234
after restarting tomcat I see it listening on port 1234
and something like 33051. This makes jmx remote a
bit difficult to use in a secure environment.
What secret am I missing? I by playing with the
iptables and the dynamic port opened for listening I can
verify that my jconsole connect failures are related to this 2nd
port.
Thanks!! Joe
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
