docs: Remove JMX monitoring sections from HTTP/2 guides

JMX is obsolete for production monitoring in 2026. The documented
examples used -Dcom.sun.management.jmxremote with ssl=false and
authenticate=false — a security anti-pattern. The Http2Protocol.jmxMetrics
property does not exist in Tomcat.

Modern alternative: Micrometer + Prometheus/Grafana or Spring Boot
Actuator endpoints, which provide HTTP-accessible metrics without
opening unauthenticated JMX ports.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: robertlazarski

src/site/xdoc/docs/http2-transport-additions.xml

@@ -278,8 +278,9 @@ sender negotiates HTTP/2 framing and flow control automatically.</p>
 
 <h3>Performance Monitoring</h3>
 
-<p>HTTP/2 transport performance can be monitored via JMX or application-level
-logging.  Enable JMX in the JVM startup flags (see the JVM Tuning section).</p>
+<p>For production monitoring, use Micrometer with Prometheus/Grafana or
+Spring Boot Actuator endpoints.  Application-level logging via the
+Axis2 log configuration provides per-request timing details.</p>
 
 <p>Available metrics include:</p>
 <ul>

src/site/xdoc/docs/openapi-rest-advanced-http2-userguide.xml

@@ -406,14 +406,8 @@ export CATALINA_OPTS="$CATALINA_OPTS -Dorg.apache.coyote.http2.Http2Protocol.ini
 # Note: Axis2 HTTP/2 and OpenAPI are configured in axis2.xml, not via
 # system properties.  No -Daxis2.* flags are needed.
 
-# Performance Monitoring
-export CATALINA_OPTS="$CATALINA_OPTS -Dcom.sun.management.jmxremote"
-export CATALINA_OPTS="$CATALINA_OPTS -Dcom.sun.management.jmxremote.port=9999"
-export CATALINA_OPTS="$CATALINA_OPTS -Dcom.sun.management.jmxremote.ssl=false"
-export CATALINA_OPTS="$CATALINA_OPTS -Dcom.sun.management.jmxremote.authenticate=false"
-
-# Tomcat HTTP/2 Metrics
-export CATALINA_OPTS="$CATALINA_OPTS -Dorg.apache.coyote.http2.Http2Protocol.jmxMetrics=true"
+# For production monitoring, use Micrometer with Prometheus/Grafana
+# or Spring Boot Actuator endpoints rather than raw JMX.
 </pre>
 
 </body>

src/site/xdoc/docs/spring-boot-starter.xml

@@ -78,7 +78,7 @@ new configurator implementation — work that is planned but not yet complete.</
 long-running, stateful service deployments typical of Axis2 workloads:</p>
 
 <ul>
-<li>Container-managed thread pools, connection pools, and JMX monitoring</li>
+<li>Container-managed thread pools, connection pools, and monitoring (Actuator/Micrometer)</li>
 <li>Hot-redeploy via exploded WAR without JVM restart</li>
 <li>Central TLS/certificate management (Tomcat's <code>server.xml</code>, WildFly's Elytron)</li>
 <li>Established operational tooling (WildFly CLI, Tomcat Manager, deployment scanners)</li>

src/site/xdoc/docs/tomcat-http2-integration-guide.xml

@@ -282,18 +282,6 @@ export CATALINA_OPTS="$CATALINA_OPTS -Daxis2.json.moshi.h2.async.threshold=10485
                 Compression:%{Accept-Encoding}i" />
 </pre>
 
-<h4>JMX Monitoring Integration</h4>
-<pre>
-# Enable JMX for HTTP/2 metrics monitoring
-export CATALINA_OPTS="$CATALINA_OPTS -Dcom.sun.management.jmxremote"
-export CATALINA_OPTS="$CATALINA_OPTS -Dcom.sun.management.jmxremote.port=9999"
-export CATALINA_OPTS="$CATALINA_OPTS -Dcom.sun.management.jmxremote.ssl=false"
-export CATALINA_OPTS="$CATALINA_OPTS -Dcom.sun.management.jmxremote.authenticate=false"
-
-# HTTP/2 specific metrics
-export CATALINA_OPTS="$CATALINA_OPTS -Dorg.apache.coyote.http2.Http2Protocol.jmxMetrics=true"
-</pre>
-
 <h2>Production Deployment Guide</h2>
 
 <h3>1. Step-by-Step Deployment</h3>