svn commit: r1060726 - in /websites/production/cxf/content: cache/docs.pageCache docs/jmx-management.html

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

svn commit: r1060726 - in /websites/production/cxf/content: cache/docs.pageCache docs/jmx-management.html

buildbot
Author: buildbot
Date: Wed May 20 15:56:44 2020
New Revision: 1060726

Log:
Production update by buildbot for cxf

Modified:
    websites/production/cxf/content/cache/docs.pageCache
    websites/production/cxf/content/docs/jmx-management.html

Modified: websites/production/cxf/content/cache/docs.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/cxf/content/docs/jmx-management.html
==============================================================================
--- websites/production/cxf/content/docs/jmx-management.html (original)
+++ websites/production/cxf/content/docs/jmx-management.html Wed May 20 15:56:44 2020
@@ -156,7 +156,7 @@ Apache CXF -- JMX Management
 </cxf:bus>
 
 </pre>
-</div></div><div class="table-wrap"><table class="wrapped confluenceTable"><colgroup span="1"><col span="1"><col span="1"></colgroup><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><img class="emoticon emoticon-warning" src="https://cwiki.apache.org/confluence/s/-7iq2vk/8301/13280cd41a592ca5883bbc1ae415b58671505365/_/images/icons/emoticons/warning.svg" data-emoticon-name="warning" alt="(warning)"></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Changes in CXF 2.5.x</strong> <br clear="none" class="atl-forced-newline">Starting from 2.5.0, if&#160;a MBeanServer is available in the Spring context or as an OSGi server (when running in OSGi), the InstrumentationManger will be automatically enabled and will use that MBeanServer and the CXF MBeans will be registered. Therefore, the instrumentation manager configuration shown above is not needed in such cases.</p></td></tr></tbody></table></div><p>To test the configuration start up your service and connect
  to it by using JConsole from the JDK. Then you can browse to your endpoint:<br clear="none"><br clear="none">&#160;<br clear="none"><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image" src="jmx-management.data/jconsole_service_endpoint.png"></span><br clear="none">&#160;</p><p><span class="confluence-anchor-link" id="JMXManagement-cxf_in_servicemix"></span></p><h1 id="JMXManagement-Remoteaccess">Remote access</h1><p>Remove access to JMX is configured using the standard JVM JMX options. For example:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><div class="table-wrap"><table class="wrapped confluenceTable"><colgroup span="1"><col span="1"><col span="1"></colgroup><tbody><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><img class="emoticon emoticon-warning" src="https://cwiki.apache.org/confluence/s/-7iq2vk/8301/13280cd41a592ca5883bbc1ae415b58671505365/_/images/icons/emoticons/warning.svg" data-emoticon-name="warning" alt="(warning)"></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><strong>Changes in CXF 2.5.x</strong> <br clear="none" class="atl-forced-newline">Starting from 2.5.0, if&#160;a MBeanServer is available in the Spring context or as an OSGi server (when running in OSGi), the InstrumentationManger will be automatically enabled and will use that MBeanServer and the CXF MBeans will be registered. Therefore, the instrumentation manager configuration shown above is not needed in such cases.</p></td></tr></tbody></table></div><p>To test the configuration start up your service and connect
  to it by using JConsole from the JDK. Then you can browse to your endpoint:<br clear="none"><br clear="none">&#160;<br clear="none"><span class="confluence-embedded-file-wrapper"><img class="confluence-embedded-image" src="jmx-management.data/jconsole_service_endpoint.png"></span><br clear="none">&#160;</p><p><span class="confluence-anchor-link" id="JMXManagement-cxf_in_servicemix"></span></p><h1 id="JMXManagement-Remoteaccess">Remote access</h1><p>Remote access to JMX is configured using the standard JVM JMX options. For example if you want to enable remote access without enabling TLS or authentication (this is extremely insecure, do not do this in production!):</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <pre class="brush: java; gutter: false; theme: Default">-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=9913 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Djava.rmi.server.hostname=localhost</pre>
 </div></div><p>Then you can connect using jconsole specifying either of the following for the remote process:</p><ul><li>localhost:9913</li><li>service:jmx:rmi:///jndi/rmi://localhost:9913/jmxrmi</li></ul><h1 id="JMXManagement-ConfiguringCXFtoUsetheServiceMix4MBeanServer">Configuring CXF to Use the ServiceMix 4 MBeanServer</h1><p>If you are embedding a CXF service in a ServiceMix 4 container, the configuration is slightly different from above. You don't want to start a new MBeanServer and you probably don't want to create additional connectors as the container manages both of these for you. You can get a reference to the container's MBeanServer through the OSGi framework and inject this reference into the JMX integration extension. Don't forget to add the Spring OSGI namespace and schemaLocation to your CXF configuration file if they are not already present.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <pre class="brush: java; gutter: false; theme: Default">