7 Replies Latest reply on Aug 19, 2008 1:09 PM by peterj

    about jbossall-client.jar in JBOSS 5.0 CR version

    chaitra

      in our application we are trying to retreive the performance data from JBOSS server version 5.0 CR release. we are not able to retreive JMS Data, we got the following exception like this

      "jboss.mq:service=MessageCache is not registered"

      Copied the jbossall-client.jar into the application . with previous version of JBOSS i.e JBOSS 4.0.3 it was working fine, now it is giving the above mentioned error.

      Is something else need to be used along with jbossall-client.jar?



        • 1. Re: about jbossall-client.jar in JBOSS 5.0 CR version
          jaikiran

          Starting JBoss-5 CR1, the jbossall-client.jar is a Manifest only jar. I don't have access to my system right now, but i remember that the jbossall-client.jar in CR1 had a ReadMe inside it, which tells you which all jars you need to copy in the client's classpath.


          we are not able to retreive JMS Data, we got the following exception like this

          "jboss.mq:service=MessageCache is not registered"


          I am not sure whether this exception is because of the missing jar files. You will have to post the entire exception stacktrace. Where does this exception occur? Is it on the client or on the server?

          • 2. Re: about jbossall-client.jar in JBOSS 5.0 CR version
            chaitra

            Hi,

            I copied all the jar files listed in readme file ,but still getting the exception and not able to collect JMS related data.

            the error is displying at the client side.

            Failed to retrieve the MBean attribute . javax.management.InstanceNotFoundException: jboss.mq:service=MessageCache is not registered.

            • 3. Re: about jbossall-client.jar in JBOSS 5.0 CR version
              jaikiran

              You will have to give us more details about what you are doing and even the contents of the server.log file.

              • 4. Re: about jbossall-client.jar in JBOSS 5.0 CR version
                chaitra

                hi,

                we are creating a monitor to collect performance data from JBOSS server related to JMS. for eg:

                Message cache hits

                Messge cache size etc.



                this is the error displayed in server.log.


                2008-08-13 11:19:31,343 DEBUG [org.jboss.invocation.http.servlet.InvokerServlet] (http-10.129.8.18-8080-1) Invoke threw exception
                org.jboss.jmx.connector.invoker.client.InvokerAdaptorException
                at org.jboss.jmx.connector.invoker.InvokerAdaptorService.invoke(InvokerAdaptorService.java:296)
                at sun.reflect.GeneratedMethodAccessor152.invoke(Unknown Source)
                at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
                at java.lang.reflect.Method.invoke(Method.java:597)
                at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
                at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
                at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:138)
                at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
                at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:140)
                at org.jboss.jmx.connector.invoker.SerializableInterceptor.invoke(SerializableInterceptor.java:74)
                at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
                at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
                at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
                at org.jboss.invocation.http.servlet.InvokerServlet.processRequest(InvokerServlet.java:162)
                at org.jboss.invocation.http.servlet.InvokerServlet.doPost(InvokerServlet.java:224)
                at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
                at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
                at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
                at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
                at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
                at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
                at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
                at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
                at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:183)
                at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:189)
                at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433)
                at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:90)
                at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:96)
                at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
                at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
                at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
                at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
                at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:325)
                at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828)
                at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601)
                at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
                at java.lang.Thread.run(Thread.java:619)[


                • 5. Re: about jbossall-client.jar in JBOSS 5.0 CR version
                  peterj

                  The mbean you are querying is for JBossMQ, which was the messaging server provided with JBossAS 4.0.x. In JBossAS 5.0, the messaging server is JBoss Messaging. Therefore, you should now be looking at one of the jboss.messaging:* MBeans (use jmx-console to find the one you want).

                  • 6. Re: about jbossall-client.jar in JBOSS 5.0 CR version
                    chaitra

                    hi,

                    In Jboss 4.0, there is mbean named jboos.mq:service=message cache, which contains attributes Hardrefcachesize,cache misses, cache hits etc..,which is the corresponding mbean in jboss 5.0 which contains these attributes, (I searched for these attributes in mbeans which are under Jboss messaging in JMX console, but not able to find these attributes)

                    • 7. Re: about jbossall-client.jar in JBOSS 5.0 CR version
                      peterj

                      If you searched through the mbeans and did not find the data points (cache misses, cache hits, etc) you were looking for, then they are not there.

                      You could ask on the JBoss Messaging forum if the messaging team intends to provide that kind of data in the future.