4 Replies Latest reply on Mar 22, 2002 7:41 AM by squirest

    JNDIView problem

      Hi,

      I am trying to move up to the beta2, but I'm having problems with JNDIView. I have changed the run.jar classpath to include jboss-jmx and the jmxri (in that order), but I get this message. Any ideas?

      Failed to getDeployedApplications
      ReflectionException: null
      Cause: java.lang.NoSuchMethodException: Unable to locate method for: getDeployedApplications()
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(Unknown Source)
      at org.jboss.mx.server.MBeanServerImpl.invoke(Unknown Source)
      at org.jboss.naming.JNDIView.list(JNDIView.java:69)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
      at java.lang.reflect.Method.invoke(Unknown Source)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(Unknown Source)
      at org.jboss.mx.server.MBeanServerImpl.invoke(Unknown Source)
      at com.sun.jdmk.comm.HtmlInvokePage.buildPage(HtmlInvokePage.java:240)
      at com.sun.jdmk.comm.HtmlRequestHandler.processGetRequest(HtmlRequestHandler.java:325)
      at com.sun.jdmk.comm.HtmlRequestHandler.processRequest(HtmlRequestHandler.java:152)
      at com.sun.jdmk.comm.HtmlRequestHandler.doRun(HtmlRequestHandler.java:79)
      at com.sun.jdmk.comm.ClientHandler.run(ClientHandler.java:84)
      at java.lang.Thread.run(Unknown Source)

      Thanks,

      John

        • 1. Re: JNDIView problem

          Hi,

          This is a bug in jboss, I'm going to fix this and
          some others this weekend.

          You can fix this yourself by changing the
          invoke() in JNDIView.list to use server.getAttribute()
          the attribute name is "DeployedApplications"

          Regards,
          Adrian

          • 2. Re: JNDIView problem
            squirest

            Hey,

            the version of JNDIView that you are using (1.12 I think) is trying to call a getter method for an attribute - something which is illegal.

            Juha/Adrian, this problem is going to come up again and again until jboss/jbossmx releases are synch'd up WRT supported behaviour. Adrian, are you able to give advice as to which JBoss version works best?

            To reiterate what I said yesterday, I think we should add a switch to relax "attribute methods are not operations". I take Adrian's point that jbossians don't like hacks but while we're trying to encourage early jbossmx adopters this sort of thing is just going to piss people off.

            Trev

            • 3. Re: JNDIView problem

              Hi Trevor,

              Yeh, somebody already fixed it. It is in latest HEAD from
              REL_3_0_0_4. But that tag has the MBeanProxy problem.

              I'm going to integrate this weekend unless I get a stop
              from the dev-list.
              I can then announce a release tag where JBoss uses
              JBossMX and the java 1.4 problem goes away. :-)

              Personally, I vote against the hack. I think the same
              problem will arise with the jmxri.jar maintenance
              release.
              It is better developers spot this mistake early, rather
              than get bitten by it in a live environment later.

              But, you've got r/w if you want to provide
              backwards compatiblity(TM)
              Just make sure it is off by default.

              Regards,
              Adrian

              • 4. Re: JNDIView problem
                squirest

                Okay,

                if you get a "stop" on the release tag I'll revisit the hack issue.

                Trev