https://issues.apache.org/bugzilla/show_bug.cgi?id=56733
--- Comment #20 from Rainer Jung <rainer.j...@kippdata.de> --- It *should* be like that (for 2.2, 2.4 should be fine): - to much memory used while requests are in process - concurrent processing of requests will multiply the needed memory - MaxMemFree allows to define, how much of that memory will be freed again after each request has finished I need to check these assumptions (probably next week) and whether I can reproduce. As Joe indicated, there might be a workaround possible. Based on the fact, that 2.4 is pretty stable and the issue only shows for huge content with flushpackets set, it is quite possible, that we won't go that way. At least it will depend on how easy the problem is to work around in code. As always: patches welcome. -- 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
