Currently any mbean that registers with the JBoss
MBeanServer is treated as a candidate implementation
of the org.jboss.util.Service interface and these
methods are invoked on it. This can have bad side
affects that range from annoying exceptions being
logged to invoking a method that has nothing to do
with being a service. There needs to be a better
classification of what mbeans are JBoss services.
Log in to post a comment.