You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AXIS2-6103 Fix remaining 65536 initialWindowSize across all HTTP/2 docs
Update all config examples and tables in WildFly, Tomcat, Spring Boot,
and integration guides to use initialWindowSize=2097152 (2MB) instead
of 65536 (64KB). The 64KB value caused ~156 WINDOW_UPDATE round-trips
per stream for 10MB responses.
Server-side buffer/flush settings (buffer-size, streamingBufferSize,
moshiStreamingBufferSize) remain at 64KB — those are serialization
flush intervals, not flow-control windows.
<tr><td><strong>http2MaxConcurrentStreams</strong></td><td>200</td><td>High multiplexing for large JSON APIs</td><td>http2-max-concurrent-streams="200"</td></tr>
147
-
<tr><td><strong>http2InitialWindowSize</strong></td><td>65536 (64KB)</td><td>Aligned with Enhanced Moshi H2 buffers</td><td>http2-initial-window-size="65536"</td></tr>
147
+
<tr><td><strong>http2InitialWindowSize</strong></td><td>2097152 (2MB)</td><td>Avoids flow-control round trips on large responses</td><td>http2-initial-window-size="2097152"</td></tr>
148
148
<tr><td><strong>http2MaxFrameSize</strong></td><td>32768 (32KB)</td><td>Optimal for JSON streaming</td><td>http2-max-frame-size="32768"</td></tr>
0 commit comments