-
1. Re: Not starting with standard Sun JMX options
dmlloyd Nov 28, 2011 1:16 PM (in response to robertobeeman)1 of 1 people found this helpfulUsing JMX RMI to manage the AS is not supported for a variety of reasons. We anticipate providing a different remote JSR-160 connection mechanism for 7.1.0.Final however.
-
2. Re: Not starting with standard Sun JMX options
jason.greene Nov 28, 2011 1:19 PM (in response to dmlloyd)David Lloyd wrote:
Using JMX RMI to manage the AS is not supported for a variety of reasons. We anticipate providing a different remote JSR-160 connection mechanism for 7.1.0.Final however.
In the meantime you can enabled it in the beta by changing your standalone.xml to add one additional line to the jmx subsystem like so:
<subsystem xmlns="urn:jboss:domain:jmx:1.1" show-model="true"> <jmx-connector registry-binding="jmx-connector-registry" server-binding="jmx-connector-server" /> </subsystem>
-
3. Re: Not starting with standard Sun JMX options
robertobeeman Nov 28, 2011 1:22 PM (in response to dmlloyd)Hi David,
Thank you for your quick update. But i am not sure how to use JSR-160 connection mechanism. Do you have any link or example which i can use in this case.
I also see a JIRA related to this isue: https://issues.jboss.org/browse/AS7-1 which says that it should have been fixed in 7.0.0.Alpha1
Thanks
Roberto
-
4. Re: Not starting with standard Sun JMX options
jason.greene Nov 28, 2011 1:20 PM (in response to jason.greene)Jason Greene wrote
In the meantime you can enabled it in the beta by changing your standalone.xml to add one additional line to the jmx subsystem like so:
Note that doing so is an unsecure option, and other users on your system will have the ability to execute any JMX operation, up to and including executing arbitrary code.
-
5. Re: Not starting with standard Sun JMX options
jason.greene Nov 28, 2011 1:21 PM (in response to jason.greene)1 of 1 people found this helpfulJason Greene wrote:
Jason Greene wrote
In the meantime you can enabled it in the beta by changing your standalone.xml to add one additional line to the jmx subsystem like so:
Note that doing so is an unsecure option, and other users on your system will have the ability to execute any JMX operation, up to and including executing arbitrary code.
Also if you are on the local system, you can still use the direct process attach feature of JMX console (and other tools that support it). This will work regardless
-
6. Re: Not starting with standard Sun JMX options
robertobeeman Nov 28, 2011 1:24 PM (in response to jason.greene)Hi Jason,
Basically i needed a standalone Java aplication Remotely to query some of the JVM MBeans on which the JBoss is running. Is it not possible.
-
7. Re: Not starting with standard Sun JMX options
dlofthouse Nov 28, 2011 1:28 PM (in response to robertobeeman)We need to implement the mechanism itself first, then we will be able to provide some guidance as to how to use it.
-
8. Re: Not starting with standard Sun JMX options
jason.greene Nov 28, 2011 1:28 PM (in response to robertobeeman)Roberto Beeman wrote:
Hi Jason,
Basically i needed a standalone Java aplication Remotely to query some of the JVM MBeans on which the JBoss is running. Is it not possible.
Ok then you can edit the standalone.xml as described above to enable it, but bear in mind that there is no security on that port, so whoever can see it can do anything they want to your system.
We are going to provide a jboss-remoting based JSR-160 implementation by 7.1 final that will allow you to do the same thing, but it will use a secure authtentication mechanism that is consistent with our other protocols. You will have to add a couple jars to your client though.
-
9. Re: Not starting with standard Sun JMX options
robertobeeman Nov 28, 2011 1:34 PM (in response to jason.greene)Hi Jason,
If i dont add the following snippet on my "standalone-full.xml" file then i see all the MBeans inside the JConsole ... inclusing JBoss MBeans and JVM MBeans.
<subsystem xmlns="urn:jboss:domain:jmx:1.1" show-model="true">
<jmx-connector registry-binding="jmx-connector-registry" server-binding="jmx-connector-server" />
</subsystem>With the above configuration my JConsole is not showing me the following MBeans "jboss.jta", "jboss.modules", "jboss.ws" and "jboss.msc" is this normal or i have done something wrong?
-
10. Re: Not starting with standard Sun JMX options
jason.greene Nov 28, 2011 1:41 PM (in response to robertobeeman)Roberto Beeman wrote:
With the above configuration my JConsole is not showing me the following MBeans "jboss.jta", "jboss.modules", "jboss.ws" and "jboss.msc" is this normal or i have done something wrong?
Any chance you picked the wrong port?
localhost:1090 is the default
-
11. Re: Not starting with standard Sun JMX options
robertobeeman Nov 28, 2011 1:56 PM (in response to jason.greene)HI Jason,
As the JConsole is automatically detecting the Local JBoss process so i am not passing and URL in the following format:
service:jmx:rmi:///jndi/rmi://localhost:1090/jmxrmi
But if i try to connect to JBoss using the Above URL in JConsole then Connection never gets established.
-
12. Re: Not starting with standard Sun JMX options
robertobeeman Nov 28, 2011 1:58 PM (in response to jason.greene)Hi Jason,
I am able to connect to JBoss using JConsole now...i made a silly mistake earlier.
Thank you ....for all your help
Thank you David.