5 Replies Latest reply on Apr 19, 2005 11:58 PM by reverbel

    Separated XMBean implementation

      This will test who subscribed to the dev-list :-)

      There is a new module in jboss-head/jboss-pojo (mbeans) that is a separation
      of the XMBean implementation from the MBeanServer implementation.
      http://jira.jboss.com/jira/browse/JBJMX-91

      To update your cvs tree

      cd jboss-head
      cvs co -d mbeans jboss-mbeans
      


      This excercise is to make sure we don't break the XMBean implementation
      (for backwards compatibility reasons) as we modify the MBeanServer for
      our pojo strategy.

        • 1. Re: Separated XMBean implementation
          reverbel

          It may have nothing to do with the XMBean change, but after updating my CVS tree I started getting this JMX-related NPE:

          [org.jboss.system.ServiceController] Problem starting service jboss:service=DistributedTransactionManager
          java.lang.NullPointerException: Failed to find method for operation: addInvocationHandler invoke on resource: org.jboss.remoting.transport.Connector@17d7c7f
           at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:136)
           at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
           at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:121)
           at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
           at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127)
           at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
           at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:246)
           at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:653)
           at org.jboss.tm.remoting.server.DistributedTransactionManager.startService(DistributedTransactionManager.java:65)
           at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
           at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
           ...
          



          • 2. Re: Separated XMBean implementation

            There should be no change by the jmx -> mbeans. All I did was move code.

            Can you tell me how to reproduce the problem (report it on JIRA).

            • 3. Re: Separated XMBean implementation
              reverbel

              Done:

              http://jira.jboss.com/jira/browse/JBJMX-92

              Before trying to reproduce the problem, please do a CVS update in the transaction and iiop subdirs. I have just committed some changes in those subdirs.

              The NPE does not happen if I copy jboss-transaction.jar and jboss-iiop.jar (the modules on which I have been working) from an up-to-date jboss-head tree (which gives me the NPE) to the generated server/all/lib subdir of an outdated jboss-head tree, which I checked out from CVS on Mar 26. The older jboss-5.0.0alpha does not throw the NPE.

              Thanks,

              Francisco

              • 4. Re: Separated XMBean implementation

                This turned out to be a change in Remoting's connector without a corresponding
                change in its XMBean descriptor:
                http://cvs.sourceforge.net/viewcvs.py/jboss/jboss-remoting/src/main/org/jboss/remoting/transport/Connector.java?r1=1.25&r2=1.26

                • 5. Re: Separated XMBean implementation
                  reverbel

                  Thank you Adrian.

                  Regards,

                  Francisco