I haven't looked at or played with the new JMX featuers. But I do have some thoughts on names and scopes. We need to ensure that there is a unique naming mechanism.
A single monitoring tool may be used to monitor multiple instances of Tomcat. I plan on doing that some time in the future. Each instance of Tomcat running needs to have a unique name.
The host name can not be used in lieu of the Engine name. I configure
two Engine's which have the same host name. One for normal http, one for https.
The scoping required to ensure unique names is /Service/Engine/Host/Context.
Did you understand that JMX domain name = engine name = unique ID ?
Remy
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
