Skip to main content
summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
Diffstat (limited to 'jetty-jmx/src/main/config/etc/jetty-jmx.xml')
-rw-r--r--jetty-jmx/src/main/config/etc/jetty-jmx.xml60
1 files changed, 22 insertions, 38 deletions
diff --git a/jetty-jmx/src/main/config/etc/jetty-jmx.xml b/jetty-jmx/src/main/config/etc/jetty-jmx.xml
index 4db0dbb473..2732c4069e 100644
--- a/jetty-jmx/src/main/config/etc/jetty-jmx.xml
+++ b/jetty-jmx/src/main/config/etc/jetty-jmx.xml
@@ -1,66 +1,50 @@
<?xml version="1.0"?>
-<!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure.dtd">
+<!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure_9_0.dtd">
-<!-- ============================================================================ -->
-<!-- To correctly start Jetty with JMX module enabled, this configuration -->
-<!-- file must appear first in the list of the configuration files. -->
-<!-- The simplest way to achieve this is to add etc/jetty-jmx.xml as the -->
-<!-- first file in configuration file list at the end of start.ini file. -->
-<!-- ============================================================================ -->
<Configure id="Server" class="org.eclipse.jetty.server.Server">
<!-- =========================================================== -->
<!-- Set the java.rmi.server.hostname property in case you've -->
<!-- got a misconfigured /etc/hosts entry or the like. -->
<!-- =========================================================== -->
- <!--
+ <!--
<Call class="java.lang.System" name="setProperty">
<Arg>java.rmi.server.hostname</Arg>
<Arg>127.0.0.1</Arg>
</Call>
-->
-
+
<!-- =========================================================== -->
- <!-- Initialize an mbean server -->
+ <!-- Get the platform mbean server -->
<!-- =========================================================== -->
<Call id="MBeanServer" class="java.lang.management.ManagementFactory"
name="getPlatformMBeanServer" />
<!-- =========================================================== -->
- <!-- Initialize the Jetty MBean container -->
+ <!-- Initialize the Jetty MBean container -->
<!-- =========================================================== -->
- <New id="MBeanContainer" class="org.eclipse.jetty.jmx.MBeanContainer">
- <Arg><Ref id="MBeanServer" /></Arg>
- <Call name="start"/>
- </New>
-
- <!-- Add to the Server to listen for object events -->
- <Get id="Container" name="container">
- <Call name="addEventListener">
- <Arg><Ref id="MBeanContainer" /></Arg>
- </Call>
- </Get>
-
- <!-- Add to the Server as a managed lifecycle -->
<Call name="addBean">
- <Arg><Ref id="MBeanContainer"/></Arg>
- <Arg type="boolean">true</Arg>
+ <Arg>
+ <New id="MBeanContainer" class="org.eclipse.jetty.jmx.MBeanContainer">
+ <Arg>
+ <Ref refid="MBeanServer" />
+ </Arg>
+ </New>
+ </Arg>
</Call>
<!-- Add the static log -->
- <Ref id="MBeanContainer">
- <Call name="addBean">
- <Arg>
- <New class="org.eclipse.jetty.util.log.Log"/>
- </Arg>
- </Call>
- </Ref>
-
+ <Call name="addBean">
+ <Arg>
+ <New class="org.eclipse.jetty.util.log.Log" />
+ </Arg>
+ </Call>
+
<!-- In order to connect to the JMX server remotely from a different
process, possibly running on a different host, Jetty JMX module
can create a remote JMX connector. It requires RMI registry to
be started prior to creating the connector server because the
- JMX specification uses RMI to facilitate connections.
+ JMX specification uses RMI to facilitate connections.
-->
<!-- Optionally start the RMI registry. Normally RMI registry runs on
@@ -75,15 +59,15 @@
</Call>
</Call>
-->
-
+
<!-- Optionally add a remote JMX connector. The parameters of the constructor
below specify the JMX service URL, and the object name string for the
- connector server bean. The parameters of the JMXServiceURL constructor
+ connector server bean. The parameters of the JMXServiceURL constructor
specify the protocol that clients will use to connect to the remote JMX
connector (RMI), the hostname of the server (local hostname), port number
(automatically assigned), and the URL path. Note that URL path contains
the RMI registry hostname and port number, that may need to be modified
- in order to comply with the firewall requirements.
+ in order to comply with the firewall requirements.
-->
<!--
<New id="ConnectorServer" class="org.eclipse.jetty.jmx.ConnectorServer">

Back to the top