Date: 2005-03-01T14:05:23
Editor: AchimHuegen
Wiki: Jakarta HiveMind Wiki
Page: JmxDoc
URL: http://wiki.apache.org/jakarta-hivemind/JmxDoc
no comment
Change Log:
------------------------------------------------------------------------------
@@ -6,11 +6,6 @@
= How to get started =
-Ok, you want to build in jmx support in your HiveMind application.
-Actually there are two topics to talk about now:
- * How do you want to connect to the application?
- * What do you want to manage?
-
For the impatient ones, that just want to get up anything to play with
here are some [#QuickStart quick start instructions].
For a more complete introduction read on [#Intro here]
@@ -58,7 +53,13 @@
}}}
-Ensure that mx4j.jar (mx4j 2.x) and log4j.jar are included in the classpath of
your application. Start the application, start jconsole and connect to the
local application.
+Ensure that mx4j.jar (mx4j 2.x) and log4j.jar are included in the classpath of
your application. Start the application with -Dcom.sun.management.jmxremote
+
+{{{
+java -Dcom.sun.management.jmxremote ...
+}}}
+
+start jconsole and connect to the local application.
[[Anchor(QuickStartResults)]]
== Quick start results ==
@@ -116,7 +117,7 @@
== HTML Connector ==
The HTTP Connector renders HTML pages for the remote management.
-Setup and configuration are specific for the jmx library you are using (that
is J2SE 1.5, Sun RI, MX4J).
+Setup and configuration are specific to the jmx library you are using (that is
J2SE 1.5, Sun RI, MX4J).
=== MX4J HTML Connector ===
@@ -144,11 +145,12 @@
{{{
<contribution configuration-id="hivemind.management.MBeans">
- <mbean service-id="hivemind.management.connector.SunHttpAdaptorMBean"
start-method="start" />
+ <mbean service-id="hivemind.management.connector.SunHttpAdaptorMBean"
+ start-method="start" />
</contribution>
}}}
-The port is configured like for MX4J.
+The port is configured like described for MX4J.
=== J2SE 1.5 and Http Connector ===
@@ -156,14 +158,16 @@
== JSR 160 Connector ==
-JSR 160 connectors are created by a standardized api so there is no
implementation specific setup like with HTTP Connectors.
-The standard allows use of different protocols for the remote management. Most
common is a RMI protocol and this is what HiveMind supports in the moment.
+JSR 160 connectors allow the remote management of the application using any
management console that supports the standard (like JConsole, MC4J).
+The connectors are created by a standardized api so there is no implementation
specific setup like with HTTP Connectors. The standard allows use of different
protocols for the remote management. Most common is a RMI protocol and this is
what HiveMind supports in the moment.
It requires a running RMI Registry. Add these lines:
{{{
<contribution configuration-id="hivemind.management.MBeans">
- <mbean service-id="hivemind.management.connector.NamingServiceMBean"
start-method="start" />
- <mbean service-id="hivemind.management.connector.JMXConnectorServerMBean"
start-method="start" />
+ <mbean service-id="hivemind.management.connector.NamingServiceMBean"
+ start-method="start" />
+ <mbean service-id="hivemind.management.connector.JMXConnectorServerMBean"
+ start-method="start" />
</contribution>
}}}
@@ -174,7 +178,8 @@
{{{
<contribution configuration-id="hivemind.ApplicationDefaults">
<default symbol="management.namingservice.port" value="1099" />
- <default symbol="management.jmxconnector.ServiceUrl"
value="service:jmx:rmi://localhost/jndi/rmi://localhost:1099/jmx"; />
+ <default symbol="management.jmxconnector.ServiceUrl"
+ value="service:jmx:rmi://localhost/jndi/rmi://localhost:1099/jmx"; />
</contribution>
}}}
@@ -190,6 +195,8 @@
{{{
java -Dcom.sun.management.jmxremote ...
}}}
+
+Connect with JConsole using the 'local' tab on the connection dialog.
== Export services as MBeans ==
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
