4 Replies Latest reply on Feb 28, 2012 10:07 AM by trevor.flanagan

    AS 7.1 Final and JMX

    trevor.flanagan

      I am trying to connect remotely using JRockit Mission Control into my jboss standalone instance. Originally I tried using the usual com.sun.management.jmxremote parameters and had no luck due to the LogManager issue that other people have seen. I then reconfigured my standalone.xml (shown below) and tried to connect using the following JMX service URL: service:jmx:rmi:///jndi/rmi://HOST:10447/jmxrmi

       

       

       

      {code:xml}

      <subsystem xmlns="urn:jboss:domain:jmx:1.1">

               <show-model value="true"/>

               <remoting-connector/> <!-- tried with value both true and false -->

      </subsystem>

      ......

         <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">

              <socket-binding name="http" port="10080"/>

              <socket-binding name="https" port="10443"/>

              <socket-binding name="management-native" interface="management" port="${jboss.management.native.port:9999}"/>

              <socket-binding name="management-http" interface="management" port="${jboss.management.http.port:10990}"/>

              <socket-binding name="management-https" interface="management" port="${jboss.management.https.port:11443}"/>

              <socket-binding name="osgi-http" interface="management" port="10090"/>

              <socket-binding name="remoting" port="10447"/>

              <socket-binding name="txn-recovery-environment" port="10712"/>

              <socket-binding name="txn-status-manager" port="10713"/>

        </socket-binding-group>

      {code}

       

      What else is it possible to try here?

       

      From some of the articles/discussions I have read they seem to say that JMX is not really supported by version 7.

       

      Is there another way in which I can connect using Mission Control?

       

      Message was edited by: Trevor Flanagan formatting

        • 1. Re: AS 7.1 Final and JMX
          dlofthouse

          Please see the following page describing how to achieve this with jconsole: -

           

          Using jconsole to connect to JMX on AS7

           

          Essentially you need to be using a remoting-jmx service URL for the connection as we now use Remoting for the communication.

          • 2. Re: AS 7.1 Final and JMX
            trevor.flanagan

            Thanks Darran for getting back to me. I had read your article which you linked to and did try the remoting url using the native management port 9999 and that also didnt work for me either.

             

            When I start my server I do see the following log message that might be relevant?

             

            18:55:35,033 INFO  [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)

             

            Are you aware of anything else I can try?

            • 3. Re: AS 7.1 Final and JMX
              dlofthouse

              Are you getting any error with the remoting-jmx URL?

               

              Also have you added the JBoss libraries to the classpath of your client?  That is going to be required to find the correct provider - I am just on a machine without AS7 installed but the client jar under the bin folder should contain the sufficient classes.

              • 4. Re: AS 7.1 Final and JMX
                trevor.flanagan

                Darran, thanks again for getting back to me. I was successful eventually, first getting JConsole to work and then moving onto JRockit Mission Control using the JConsole classpath. I did the following:

                 

                Copied modules folder across to my local machine from JBOSS_HOME.

                 

                Create new Application User using the add_users.sh script

                 

                Launched mission control as follows adding the classpath to the -J-Xbootclasspath/a: parameter

                 

                jrmc.exe -J-Xbootclasspath/a:C:\Users\tflanagan\modules\org\jboss\remoting3\remoting-jmx\main\remoting-jmx-1.0.0.Final.jar;C:\Users\tflanagan\modules\org\jboss\remoting3\main\jboss-remoting-3.2.2.GA.jar;C:\Users\tflanagan\modules\org\jboss\logging\main\jboss-logging-3.1.0.GA.jar;C:\Users\tflanagan\modules\org\jboss\xnio\main\xnio-api-3.0.3.GA.jar;C:\Users\tflanagan\modules\org\jboss\xnio\nio\main\xnio-nio-3.0.3.GA.jar;C:\Users\tflanagan\modules\org\jboss\sasl\main\jboss-sasl-1.0.0.Final.jar;C:\Users\tflanagan\modules\org\jboss\marshalling\main\jboss-marshalling-1.3.9.GA.jar;C:\Users\tflanagan\modules\org\jboss\marshalling\river\main\jboss-marshalling-river-1.3.9.GA.jar

                 

                Created connection with custom jmx url eg service:jmx:remoting-jmx://HOST:REMOTING_PORT

                 

                Thanks for your help on this

                1 of 1 people found this helpful