0 Replies Latest reply on Jul 10, 2009 2:26 PM by Ken M

    JBoss ServiceMBeanSupport Lifecycle Confusion

    Ken M Newbie

      Hi guys - Long time first time, blah..

      I've been using JBoss for years, but this is the first time I really needed to hook into a ServiceMBean's life cycle.

      It seemed rather easy, extend ServiceMBeanSupport - override startService() and stopService() and done..

      But it's not working properly for me.

      My Service is created, although I don't get createService() or create() called.

      I started a thread in the constructor to watch the ServiceMBeanSupport's "getStatus()" response, and I see it go from "Unregistered" to "Registered" and that's it.

      Nothing else.

      I've overridden with log messages: start() stop() create() destroy() startService() stopService() createService() destroyService() and NONE of these methods are being hit.

      I can access my ServiceMBean from the JMX console, which shows none of these lifecycle operations (not sure if it should, but it doesn't). If I create the "public void startService()" method in my MBean interface, I can now see it in the JMX console, and even call it from there -- but JBoss itself refuses to use it.

      Is there an issue with extending an abstract class that extends the ServiceSupportMBean abstract class causing the JBoss to stop the life cycles operations?

      My 2 classes are defined as:

      public abstract class AbstractService<P extends Provider, M extends Portal> extends org.jboss.system.ServiceMBeanSupport implements AbstractServiceMBean
      

      and the concrete one:
      public class MYPortalService extends AbstractService<ProviderMBean, PortalMBean>
      

      I could really use a hint here.

      P