https://issues.apache.org/bugzilla/show_bug.cgi?id=56733
--- Comment #2 from Christopher Schultz <ch...@christopherschultz.net> --- The max_packet_size is the default (8192) so that's not likely it. The connection_pool sizes are likely the differentiating factor. Did you build mod_jk yourself, or use a pre-built one? Do you know what version of APR is being used under the hood? The call mod_jk makes to ap_rflush looks fairly innocuous. That call is also made in ws_write if the request is for headers only (e.g. a HEAD request). Can you try this with and without +FlushPackets and try a huge number of HEAD requests to see if you can also trigger a memory leak? -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
