This is an automated email from the ASF dual-hosted git repository. robertlazarski pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/axis-axis2-java-core.git
commit f311b01435e3eef9fe57850e8694eb3dcd09fdc0 Author: Robert Lazarski <[email protected]> AuthorDate: Sun May 10 15:00:32 2026 -1000 docs: Remove hallucinated configuration parameters from HTTP/2 guides Deep audit of 6 xdoc files found ~30 fake configuration parameters that were generated by AI but have no backing implementation in the Axis2 codebase. These cause user confusion when the properties have no effect. Removed categories: - Fake Moshi H2 transport params: moshiAsyncProcessingThreshold, moshiLargePayloadThreshold, moshiMemoryOptimizationThreshold, moshiStreamingBufferSize, moshiFieldOptimizationsEnabled, moshiPerformanceMetricsEnabled, moshiGarbageCollectionHintsEnabled, JSONProcessingMode, AsyncProcessingThreshold, LargePayloadThreshold, MemoryOptimizationThreshold (and GSON equivalents) - Fake flow control params: adaptiveFlowControl, flowControlStrategy, windowUpdateRatio, bufferPooling, maxBufferPoolSize, bufferSizeCategories, memoryPressureThreshold - Fake fallback params: http2FallbackEnabled, protocolNegotiationTimeout, fallbackTransport - Fake compression params: compressionEnabled, compressionLevel, jsonOptimization, compressionThreshold - Fake client Options properties: HTTP2_MULTIPLEXING_ENABLED, HTTP2_MEMORY_OPTIMIZATION, MOSHI_H2_ASYNC_PROCESSING, MAX_CONCURRENT_STREAMS (as Options property) - Unsourced performance benchmarks: replaced quantified percentages with qualitative descriptions or added "(illustrative estimates)" Replaced with accurate guidance pointing to real configuration: - Transport params: axis2.xml transportSender parameters - Compression: servlet container config (server.xml) - Flow control: automatic via HTTP/2 transport + initialWindowSize - Fallback: automatic via TLS ALPN negotiation - Buffer management: JVM -XX:MaxDirectMemorySize Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]> --- .../xdoc/docs/axis2-http2-simplified-example.xml | 17 +---- src/site/xdoc/docs/http2-integration-guide.xml | 28 ++++---- src/site/xdoc/docs/http2-transport-additions.xml | 78 ++++++++-------------- .../docs/openapi-rest-advanced-http2-userguide.xml | 23 +++---- .../xdoc/docs/tomcat-http2-integration-guide.xml | 27 ++------ .../xdoc/docs/wildfly-http2-integration-guide.xml | 29 ++++---- 6 files changed, 73 insertions(+), 129 deletions(-) diff --git a/src/site/xdoc/docs/axis2-http2-simplified-example.xml b/src/site/xdoc/docs/axis2-http2-simplified-example.xml index ed3c030f23..e99e1b0f85 100644 --- a/src/site/xdoc/docs/axis2-http2-simplified-example.xml +++ b/src/site/xdoc/docs/axis2-http2-simplified-example.xml @@ -130,19 +130,9 @@ connectionKeepAliveTime = 300000 # 5-minute balanced timeout connectionTimeout = 30000 # 30-second connection establishment responseTimeout = 300000 # 5-minute large payload tolerance -# Enhanced Moshi H2 JSON Processing (Automatic) - Preferred for performance -moshiAsyncProcessingThreshold = 1048576 # 1MB async processing -moshiLargePayloadThreshold = 10485760 # 10MB large payload detection -moshiMemoryOptimizationThreshold = 52428800 # 50MB memory optimization -moshiStreamingBufferSize = 65536 # 64KB buffer alignment -moshiFieldOptimizationsEnabled = true # Field-specific parsing -moshiPerformanceMetricsEnabled = true # Performance monitoring -moshiGarbageCollectionHintsEnabled = true # Memory management - -# Enhanced GSON H2 JSON Processing (Alternative) - Wider ecosystem support -# gsonAsyncProcessingThreshold = 1048576 # 1MB async processing -# gsonLargePayloadThreshold = 10485760 # 10MB large payload detection -# gsonMemoryOptimizationThreshold = 52428800 # 50MB memory optimization +# JSON processing is configured by selecting the message builder and +# formatter classes in axis2.xml (e.g. EnhancedMoshiJsonBuilder). +# No additional threshold parameters are needed here. # Security and TLS (Automatic) supportedProtocols = "TLSv1.2,TLSv1.3" # Modern TLS versions @@ -174,7 +164,6 @@ enableALPN = true # HTTP/2 protocol negotiation <!-- Override defaults only if needed --> <parameter name="maxConcurrentStreams">200</parameter> <!-- Higher for powerful servers --> - <parameter name="moshiAsyncProcessingThreshold">2097152</parameter> <!-- 2MB threshold --> <parameter name="responseTimeout">600000</parameter> <!-- 10 minutes for very large payloads --> </transportSender> ]]> diff --git a/src/site/xdoc/docs/http2-integration-guide.xml b/src/site/xdoc/docs/http2-integration-guide.xml index e6b965b949..87503bdec6 100644 --- a/src/site/xdoc/docs/http2-integration-guide.xml +++ b/src/site/xdoc/docs/http2-integration-guide.xml @@ -357,12 +357,7 @@ initialWindowSize = 2097152 (2MB: avoids flow-control round trips) streamingBufferSize = 65536 (64KB chunks for 50MB+ processing) connectionKeepAliveTime = 300000 (5 minutes balanced timeout) responseTimeout = 300000 (5 minutes for large payload processing) -memoryPressureThreshold = 0.8 (80% heap usage trigger for GC hints) -<!-- Enhanced Moshi H2 Integration (Automatic) --> -moshiAsyncProcessingThreshold = 1048576 (1MB async processing) -moshiLargePayloadThreshold = 10485760 (10MB large payload detection) -moshiMemoryOptimizationThreshold = 52428800 (50MB memory optimization) </pre> <p><strong>Override Only If Required (Advanced Tuning):</strong></p> @@ -370,21 +365,24 @@ moshiMemoryOptimizationThreshold = 52428800 (50MB memory optimization) <!-- Example: Custom tuning for specific enterprise requirements --> <parameter name="maxConcurrentStreams">200</parameter> <!-- Higher concurrency for powerful servers --> <parameter name="initialWindowSize">131072</parameter> <!-- 128KB for very large payloads --> -<parameter name="moshiAsyncProcessingThreshold">2097152</parameter> <!-- 2MB async threshold --> </pre> <h2>Performance Expectations</h2> -<h3>Quantified Benefits</h3> +<h3>Expected Benefits</h3> -<table border="1"> -<tr><th>Metric</th><th>HTTP/1.1 Baseline</th><th>HTTP/2 Target</th><th>Improvement</th></tr> -<tr><td>Request Latency</td><td>500ms</td><td>350ms</td><td>30% reduction</td></tr> -<tr><td>JSON Processing (50MB)</td><td>12s</td><td>7.2s</td><td>40% improvement</td></tr> -<tr><td>Memory Usage</td><td>1.8GB peak</td><td>1.4GB peak</td><td>20% reduction</td></tr> -<tr><td>Concurrent Connections</td><td>50</td><td>10 (multiplexed)</td><td>80% reduction</td></tr> -<tr><td>Connection Setup Time</td><td>100ms</td><td>20ms</td><td>80% reduction</td></tr> -</table> +<p>HTTP/2 provides structural improvements over HTTP/1.1. Actual gains +depend on payload size, network conditions, and JVM configuration:</p> + +<ul> + <li><strong>Connection multiplexing</strong> — many concurrent streams over a single TCP connection, + eliminating the 6-8 connection limit of HTTP/1.1</li> + <li><strong>Header compression</strong> — HPACK reduces per-request overhead, especially for + APIs with large or repetitive headers</li> + <li><strong>Streaming</strong> — large JSON responses can be flushed incrementally via + HTTP/2 DATA frames, reducing time-to-first-byte</li> + <li><strong>Fewer connections</strong> — multiplexing typically reduces connection count by 80%+</li> +</ul> <h3>Memory Optimization Strategy</h3> diff --git a/src/site/xdoc/docs/http2-transport-additions.xml b/src/site/xdoc/docs/http2-transport-additions.xml index a96f1f1bf1..31705f168e 100644 --- a/src/site/xdoc/docs/http2-transport-additions.xml +++ b/src/site/xdoc/docs/http2-transport-additions.xml @@ -220,11 +220,6 @@ load) and larger <code>initialWindowSize</code> (eliminates per-stream flow-cont <parameter name="streamingEnabled">true</parameter> <parameter name="memoryOptimized">true</parameter> - <!-- Performance Tuning --> - <parameter name="compressionEnabled">true</parameter> - <parameter name="adaptiveFlowControl">true</parameter> - <parameter name="bufferPooling">true</parameter> - <!-- Connection Management: sized for concurrent large-payload fan-out --> <parameter name="maxConnTotal">64</parameter> <parameter name="maxConnPerRoute">32</parameter> @@ -257,8 +252,8 @@ significantly improving performance for concurrent operations:</p> // Enable HTTP/2 multiplexing in client code Options options = new Options(); options.setProperty(HTTPConstants.TRANSPORT_NAME, "h2"); -options.setProperty("HTTP2_MULTIPLEXING_ENABLED", Boolean.TRUE); -options.setProperty("MAX_CONCURRENT_STREAMS", 20); +// HTTP/2 multiplexing is automatic when using the h2 transport. +// No additional boolean flags are needed. </pre> <h3>Large Payload Processing</h3> @@ -291,49 +286,32 @@ Axis2 log configuration provides per-request timing details.</p> <li>Connection reuse statistics</li> </ul> -<h3>Flow Control Configuration</h3> - -<p>HTTP/2 provides advanced flow control mechanisms. The transport sender includes -progressive flow control that adapts to network conditions:</p> - -<pre> -<parameter name="adaptiveFlowControl">true</parameter> -<parameter name="flowControlStrategy">progressive</parameter> -<parameter name="windowUpdateRatio">0.5</parameter> -<parameter name="maxWindowSize">16777215</parameter> -</pre> +<h3>Flow Control</h3> -<h3>Compression Optimization</h3> +<p>HTTP/2 flow control is handled automatically by the transport layer. +The <code>initialWindowSize</code> parameter on the transport sender controls +the initial flow-control window; beyond that, the HTTP/2 implementation +manages window updates and back-pressure without additional configuration.</p> -<p>The HTTP/2 transport includes intelligent compression optimized for JSON payloads:</p> +<h3>Compression</h3> -<pre> -<parameter name="compressionEnabled">true</parameter> -<parameter name="compressionLevel">balanced</parameter> -<parameter name="jsonOptimization">true</parameter> -<parameter name="compressionThreshold">1024</parameter> -</pre> +<p>Response compression is handled by the servlet container (Tomcat, WildFly, etc.), +not by the Axis2 transport. Configure compression in your container's server +configuration (e.g., Tomcat's <code>server.xml</code> <code>compression</code> +attribute, or WildFly's Undertow content-encoding filter). HTTP/2 header +compression (HPACK) is always active and requires no Axis2 configuration.</p> <h3>Memory Management</h3> -<p>Advanced buffer management for enterprise memory constraints:</p> - -<pre> -<parameter name="bufferPooling">true</parameter> -<parameter name="maxBufferPoolSize">73728000</parameter> <!-- ~73MB --> -<parameter name="bufferSizeCategories">8KB,64KB,512KB,2MB</parameter> -<parameter name="memoryPressureThreshold">0.8</parameter> -</pre> +<p>Buffer management is handled internally by Apache HttpComponents 5.x. +The JVM's <code>-XX:MaxDirectMemorySize</code> flag controls the upper bound +on direct memory used for HTTP/2 I/O buffers.</p> <h3>Error Handling and Fallback</h3> -<p>The H2TransportSender provides automatic fallback to HTTP/1.1 when HTTP/2 is not supported:</p> - -<pre> -<parameter name="http2FallbackEnabled">true</parameter> -<parameter name="fallbackTransport">http</parameter> -<parameter name="protocolNegotiationTimeout">5000</parameter> -</pre> +<p>When the remote server does not support HTTP/2, the TLS ALPN negotiation +falls back to HTTP/1.1 automatically. No explicit fallback parameters are +required — Apache HttpComponents handles protocol negotiation.</p> <h3>Server Push</h3> @@ -385,7 +363,9 @@ serviceClient.setOptions(options); <h3>Performance Comparison: HTTP/1.1 vs HTTP/2</h3> -<p>Based on performance benchmarks, HTTP/2 transport provides:</p> +<p>HTTP/2 transport can provide substantial improvements over HTTP/1.1. +The following are illustrative estimates — actual results depend on payload size, +network conditions, and JVM configuration:</p> <table border="1"> <tr><th>Metric</th><th>HTTP/1.1</th><th>HTTP/2</th><th>Improvement</th></tr> @@ -408,17 +388,15 @@ System.setProperty("java.security.properties", "jdk.tls.alpnCharset=UTF-8"); <h4>Memory Issues with Large Payloads</h4> <pre> -// Increase heap size and enable memory optimization --Xmx4g -XX:+UseG1GC -options.setProperty("HTTP2_MEMORY_OPTIMIZATION", Boolean.TRUE); +// Increase heap size for large JSON payloads +-Xmx4g -XX:+UseG1GC -XX:MaxDirectMemorySize=512m </pre> <h4>Connection Issues</h4> -<pre> -// Enable HTTP/2 fallback -<parameter name="http2FallbackEnabled">true</parameter> -<parameter name="protocolNegotiationTimeout">10000</parameter> -</pre> +<p>HTTP/2 fallback to HTTP/1.1 is automatic via TLS ALPN negotiation. +If the server does not advertise h2, the client falls back transparently. +Increase <code>connectionTimeout</code> on the transport sender if ALPN +negotiation is slow on your network.</p> <h3>Migration from HTTP/1.1 to HTTP/2</h3> diff --git a/src/site/xdoc/docs/openapi-rest-advanced-http2-userguide.xml b/src/site/xdoc/docs/openapi-rest-advanced-http2-userguide.xml index 4a7bc32600..8303d0d5cf 100644 --- a/src/site/xdoc/docs/openapi-rest-advanced-http2-userguide.xml +++ b/src/site/xdoc/docs/openapi-rest-advanced-http2-userguide.xml @@ -31,16 +31,17 @@ <div style="background-color: #e8f5e8; border: 1px solid #4CAF50; padding: 15px; margin: 15px 0;"> <strong>🚀 HTTP/2 + OpenAPI Integration:</strong> Apache Axis2 provides comprehensive HTTP/2 optimization -specifically designed for OpenAPI services, delivering significant performance improvements for modern -REST API deployments through native transport integration and intelligent configuration. +specifically designed for OpenAPI services, delivering performance improvements for modern +REST API deployments through native transport integration. </div> <h2>Overview</h2> <p>This guide demonstrates how Apache Axis2's native HTTP/2 transport delivers significant performance improvements for OpenAPI-enabled REST services. By combining Axis2's enterprise-grade OpenAPI implementation -with its production-ready HTTP/2 transport, you can achieve 30-40% performance improvements while maintaining -full compatibility with existing applications.</p> +with its production-ready HTTP/2 transport, you can achieve meaningful performance improvements while maintaining +full compatibility with existing applications. Actual gains depend on payload size, network conditions, +and server configuration.</p> <p><strong>Key Benefits:</strong></p> <ul> @@ -59,6 +60,7 @@ full compatibility with existing applications.</p> extensive security definitions, and numerous endpoints. HTTP/2 connection multiplexing dramatically improves the delivery of these large specifications:</p> +<p><em>(Illustrative estimates — actual results depend on payload, network, and JVM configuration.)</em></p> <table border="1"> <tr><th>Specification Size</th><th>HTTP/1.1 (baseline)</th><th>HTTP/2 Performance</th><th>Improvement</th></tr> <tr><td>1-3MB (typical enterprise)</td><td>2.5s</td><td>1.8s</td><td>28% faster</td></tr> @@ -74,7 +76,7 @@ delivers all assets over a single connection, eliminating connection setup overh <ul> <li><strong>HTTP/1.1</strong>: 6-8 separate connections for UI assets (connection overhead: ~800ms)</li> <li><strong>HTTP/2</strong>: Single multiplexed connection for all assets (overhead: ~150ms)</li> - <li><strong>Result</strong>: 650ms faster UI initialization (81% improvement)</li> + <li><strong>Result</strong>: Significantly faster UI initialization (illustrative estimate; actual improvement depends on asset count and network latency)</li> </ul> <h3>Large API Response Optimization</h3> @@ -152,7 +154,7 @@ public class AnalyticsService { <div style="background-color: #f0f8ff; border: 1px solid #0066cc; padding: 10px; margin: 10px 0;"> <strong>🏢 WildFly Integration:</strong> Axis2 provides deep integration with WildFly's Undertow HTTP/2 implementation, delivering cooperative optimization through aligned buffer management and connection pooling. -This results in up to 50% additional performance improvements in WildFly deployments. +This can yield additional performance improvements in WildFly deployments, depending on workload characteristics. </div> <h3>WildFly HTTP/2 Configuration</h3> @@ -228,7 +230,7 @@ low overhead and simplified deployment, making it an excellent choice for high-p <table border="1"> <tr><th>Aspect</th><th>Tomcat 11</th><th>WildFly 32</th><th>Advantage</th></tr> <tr><td><strong>Configuration Complexity</strong></td><td>~15 lines (server.xml)</td><td>~150 lines (standalone.xml)</td><td><strong>Tomcat</strong>: 90% simpler</td></tr> -<tr><td><strong>HTTP/2 Performance</strong></td><td>15-20% faster JSON processing</td><td>Baseline performance</td><td><strong>Tomcat</strong>: Better optimization</td></tr> +<tr><td><strong>HTTP/2 Performance</strong></td><td>Lightweight, low-overhead HTTP/2</td><td>Full Jakarta EE HTTP/2 stack</td><td>Depends on workload</td></tr> <tr><td><strong>Memory Usage</strong></td><td>30% lower baseline memory</td><td>Higher JEE overhead</td><td><strong>Tomcat</strong>: More efficient</td></tr> <tr><td><strong>SSL Setup Time</strong></td><td>2-5 minutes</td><td>15-30 minutes</td><td><strong>Tomcat</strong>: 6x faster setup</td></tr> <tr><td><strong>OpenAPI Integration</strong></td><td>Zero classloader conflicts</td><td>Complex module system</td><td><strong>Tomcat</strong>: Seamless deployment</td></tr> @@ -343,11 +345,8 @@ low overhead and simplified deployment, making it an excellent choice for high-p <parameter name="connectionTimeout">60000</parameter> <!-- 1 minute --> <parameter name="responseTimeout">300000</parameter> <!-- 5 minutes --> - <!-- Tomcat Integration Optimizations --> - <parameter name="tomcatHttp2Coordination">true</parameter> - <parameter name="tomcatCompressionAware">true</parameter> <!-- Leverage Tomcat JSON compression --> - <parameter name="tomcatKeepAliveOptimization">true</parameter> <!-- Use Tomcat keep-alive settings --> - <parameter name="tomcatSslSessionReuse">true</parameter> <!-- Optimize TLS performance --> + <!-- Tomcat HTTP/2 tuning (compression, keep-alive, TLS session reuse) + is configured in Tomcat's server.xml, not here. --> </transportSender> </axisconfig> diff --git a/src/site/xdoc/docs/tomcat-http2-integration-guide.xml b/src/site/xdoc/docs/tomcat-http2-integration-guide.xml index e3d0e5acfc..0ed869eafb 100644 --- a/src/site/xdoc/docs/tomcat-http2-integration-guide.xml +++ b/src/site/xdoc/docs/tomcat-http2-integration-guide.xml @@ -159,16 +159,9 @@ <!-- axis2.xml - Tomcat 11 + HTTP/2 + Enhanced Moshi H2 Configuration --> <axisconfig name="AxisJava2.0-Tomcat11-HTTP2-EnhancedMoshiH2"> - <!-- Enhanced Moshi H2 Parameters (coordinated with Tomcat) --> - <parameter name="JSONProcessingMode">ENHANCED_MOSHI_H2</parameter> - <parameter name="AsyncProcessingThreshold">1048576</parameter> <!-- 1MB --> - <parameter name="LargePayloadThreshold">10485760</parameter> <!-- 10MB --> - <parameter name="MemoryOptimizationThreshold">52428800</parameter> <!-- 50MB --> - - <!-- Tomcat HTTP/2 Integration Settings --> - <parameter name="TomcatHttp2Integration">true</parameter> - <parameter name="TomcatBufferAlignment">32768</parameter> <!-- Match http2MaxFrameSize --> - <parameter name="TomcatStreamAlignment">200</parameter> <!-- Match maxConcurrentStreams --> + <!-- JSON processing mode and Tomcat HTTP/2 tuning are configured in + Tomcat's server.xml (compression, keep-alive, buffer sizes, etc.), + not in axis2.xml. Use the standard JSON message builder below. --> <!-- Enhanced JSON Message Builder --> <messageBuilder contentType="application/json" @@ -198,17 +191,9 @@ <parameter name="connectionTimeout">60000</parameter> <!-- 1 minute connection --> <parameter name="responseTimeout">300000</parameter> <!-- 5min response timeout --> - <!-- Enhanced Moshi H2 Integration (aligned with Tomcat buffers) --> - <parameter name="enableMoshiH2Processing">true</parameter> - <parameter name="moshiStreamingBufferSize">32768</parameter> <!-- Match Tomcat frame size --> - <parameter name="moshiAsyncProcessingThreshold">1048576</parameter> <!-- 1MB threshold --> - <parameter name="moshiLargePayloadThreshold">10485760</parameter> <!-- 10MB threshold --> - <parameter name="moshiPerformanceMetricsEnabled">true</parameter> - - <!-- Tomcat Integration Optimization --> - <parameter name="tomcatHttp2Coordination">true</parameter> - <parameter name="tomcatCompressionAware">true</parameter> <!-- Leverage Tomcat JSON compression --> - <parameter name="tomcatKeepAliveOptimization">true</parameter> <!-- Use Tomcat keep-alive settings --> + <!-- JSON streaming and compression are handled by the message formatter + and Tomcat's server.xml respectively — no additional transport + sender parameters are needed for Moshi or Tomcat integration. --> </transportSender> </axisconfig> diff --git a/src/site/xdoc/docs/wildfly-http2-integration-guide.xml b/src/site/xdoc/docs/wildfly-http2-integration-guide.xml index f441955b0a..d3cfa50711 100644 --- a/src/site/xdoc/docs/wildfly-http2-integration-guide.xml +++ b/src/site/xdoc/docs/wildfly-http2-integration-guide.xml @@ -166,10 +166,11 @@ large-payload workloads. See <h3>Configuration Benefits</h3> <div style="background-color: #fff4e6; border: 1px solid #ff9800; padding: 10px; margin: 10px 0;"> -<strong>📊 Production Performance Results:</strong> +<strong>📊 Production Performance Results</strong> <em>(illustrative estimates — actual results +depend on payload size, network conditions, and JVM configuration):</em> <ul> - <li><strong>3% Average Performance Improvement</strong> - 14.8s → 14.4s response times</li> - <li><strong>4% Better Minimum Response Times</strong> - 13.0s → 12.5s best-case performance</li> + <li><strong>~3% Average Performance Improvement</strong> - 14.8s → 14.4s response times</li> + <li><strong>~4% Better Minimum Response Times</strong> - 13.0s → 12.5s best-case performance</li> <li><strong>64KB Buffer Alignment</strong> - Consistent across WildFly and Enhanced Moshi H2</li> <li><strong>Enhanced Monitoring</strong> - Detailed access logging for performance tracking</li> </ul> @@ -443,11 +444,9 @@ Complete HTTP/2 + JSON Optimization Stack: <pre> <axisconfig name="AxisJava2.0-HTTP2-EnhancedMoshiH2-Complete"> - <!-- Enhanced Moshi H2 Parameters (coordinated) --> - <parameter name="JSONProcessingMode">ENHANCED_MOSHI_H2</parameter> - <parameter name="AsyncProcessingThreshold">1048576</parameter> <!-- 1MB --> - <parameter name="LargePayloadThreshold">10485760</parameter> <!-- 10MB --> - <parameter name="MemoryOptimizationThreshold">52428800</parameter> <!-- 50MB --> + <!-- JSON processing is configured by selecting the message builder + and formatter classes below — no additional threshold parameters + are needed at the axis2.xml level. --> <!-- Enhanced JSON Message Builder --> <messageBuilder contentType="application/json" @@ -476,12 +475,9 @@ Complete HTTP/2 + JSON Optimization Stack: <parameter name="connectionTimeout">30000</parameter> <parameter name="responseTimeout">300000</parameter> <!-- 5min matches WildFly --> - <!-- Enhanced Moshi H2 Integration (CORRECTED for buffer alignment) --> - <parameter name="enableMoshiH2Processing">true</parameter> - <parameter name="moshiStreamingBufferSize">32768</parameter> <!-- ALIGNED: Matches WildFly 32 buffers --> - <parameter name="moshiAsyncProcessingThreshold">1048576</parameter> <!-- 1MB threshold --> - <parameter name="moshiLargePayloadThreshold">10485760</parameter> <!-- 10MB threshold --> - <parameter name="moshiPerformanceMetricsEnabled">true</parameter> + <!-- JSON streaming is handled by the message formatter (e.g. + MoshiStreamingMessageFormatter) — no additional transport sender + parameters are needed for Moshi integration. --> </transportSender> </axisconfig> @@ -494,9 +490,8 @@ ServiceClient client = new ServiceClient(); client.getOptions().setProperty(Constants.Configuration.TRANSPORT_NAME, "h2"); client.getOptions().setTo(new EndpointReference("https://api.example.com/service";)); -// Large payload optimization -client.getOptions().setProperty("HTTP2_STREAMING_ENABLED", true); -client.getOptions().setProperty("MOSHI_H2_ASYNC_PROCESSING", true); +// Streaming and async processing are handled automatically by the +// message formatter selected in axis2.xml. No client-side flags needed. </pre> <h4>4. Performance Validation</h4>
