5 Replies Latest reply on May 14, 2003 11:23 AM by Robert

    JMX Console Empty?

    Terry Rosenbaum Newbie


      Just checked out/built Branch_3_2 from CVS. This time
      the built release directory is named jboss-3.2.0RC4.
      Previous version I built was named jboss-3.2.0RC3 (a
      week or two ago). I ran JBoss by going to the
      build/output/jboss-3.2.0RC4/bin dir and typing run.
      This is on Win2K.

      The jmx-console when viewed via http://localhost:8080/jmx-console is empty except for its page header.

      When running the jboss-3.2.0RC3 version, the jmx-console shows a bunch of MBeans.

      Does anyone have any idea of what has changed, whether or
      not this is a bug, or how to solve the problem?


        • 1. Re: JMX Console Empty?
          Adrian Brock Master

          Is there an error in the log?


          • 2. Re: JMX Console Empty?
            Terry Rosenbaum Newbie

            NullPointerException may be related. Full log available
            upon request from Terry@amicas.com (attach file didn't

            2003-03-20 08:37:56,269 DEBUG [org.jboss.management.j2ee.factory.WebModuleFactory] Created servlet: jboss.web:Jetty=0,JBossWebApplicationContext=0,context=/invoker,name=ReadOnlyAccessFilter, module: jboss.management.local:J2EEApplication=http-invoker.sar,J2EEServer=Local,WebModule=invoker.war,j2eeType=Servlet,name=ReadOnlyAccessFilter
            2003-03-20 08:37:56,269 DEBUG [org.jboss.management.j2ee.factory.WebModuleFactory] Creating servlet: jboss.web:Jetty=0,JBossWebApplicationContext=0,context=/invoker,HashSessionManager=0
            2003-03-20 08:37:56,269 DEBUG [org.jboss.management.j2ee.Servlet] Could not create JSR-77 Servlet: null
            at java.util.Hashtable.put(Hashtable.java:375)
            at org.jboss.management.j2ee.J2EEManagedObject.(J2EEManagedObject.java:147)
            at org.jboss.management.j2ee.Servlet.(Servlet.java:88)
            at org.jboss.management.j2ee.Servlet.create(Servlet.java:47)
            at org.jboss.management.j2ee.factory.WebModuleFactory.createServlet(WebModuleFactory.java:110)
            at org.jboss.management.j2ee.factory.WebModuleFactory.create(WebModuleFactory.java:49)
            at org.jboss.management.j2ee.LocalJBossServerDomain.handleNotification(LocalJBossServerDomain.java:362)
            at org.jboss.mx.server.NotificationListenerProxy.handleNotification(NotificationListenerProxy.java:71)
            at javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:82)
            at org.jboss.deployment.SubDeployerSupport.start(SubDeployerSupport.java:178)
            at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:359)
            at org.jboss.deployment.MainDeployer.start(MainDeployer.java:832)
            at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:640)
            at org.jboss.deployment.MainDeployer.addDeployer(MainDeployer.java:245)
            at java.lang.reflect.Method.invoke(Native Method)
            at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
            at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
            at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
            at $Proxy17.addDeployer(Unknown Source)
            at org.jboss.deployment.SubDeployerSupport.startService(SubDeployerSupport.java:108)
            at org.jboss.jetty.JettyService.startService(JettyService.java:171)

            • 3. Re: JMX Console Empty?
              Adrian Brock Master

              That is a DEBUG message not an error.
              It is working for me, maybe you downloaded the
              source part way through a checkin?


              • 4. Re: JMX Console Empty?
                Terry Rosenbaum Newbie

                Works fine in 3.2 RC5. I have yet to try, but presume
                it works fine in 3.2.0 final also.

                • 5. Re: JMX Console Empty?
                  Robert Newbie

                  I see this problem using 3.2.0 (with jetty), and I set the Java2ClassLoadingCompliance attribute to false on jboss.web.WebServer.

                  I was searching the list to see if anyone else encountered the same problem. This was the closest I saw.

                  This presents a bit of a problem for our team since
                  all of our wars are set up to take advantage of servlet2.3 assoc. behavior. I suppose I could just put
                  the wars into an ear and use a separate classloader.

                  Maybe this is releated - maybe not.