https://issues.apache.org/bugzilla/show_bug.cgi?id=56733
--- Comment #10 from Andy Wang <do...@moonteeth.com> --- Couple of more datapoints. Committed heap stabilized out at 35684k with: worker.tomcat1.connection_pool_timeout=0 or with worker.tomcat1.connection_pool_timeout=900 worker.maintain=900 With just worker.tomcat1.connection_pool_timeout=900 worker.maintain=60 memory grew to around 196MB before I killed the ab Here's the thing I don't understand with: worker.tomcat1.connection_pool_timeout=900 worker.maintain=60 The memory grew to about 196mb in <500s. So none of connection pool should have been recycled yet. This seems to imply that the maintenance alone is enough to "trigger" the leak. At least that's what I'm concluding from the data. Thoughts? -- 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
