The only time this happens is if you treat the mbean as a jboss service
mbean and have the ServiceController manage a lifecycle op. If you don't
do this there is no confusion over what is managing the mbean.
Brian Stansberry wrote:
I'm concerned there is going to be a problem with Tomcat
components
(connectors, valves, managers, etc) that Tomcat will want to register in
JMX. You mentioned earlier that "Subsequent use of this mbean as a
jboss mbean service can result in the ServiceController taking ownership
of the mbean"; I'm not quite sure what kinds of use will trigger this.