https://issues.apache.org/bugzilla/show_bug.cgi?id=46957
--- Comment #2 from martin.r...@centrum.cz 2009-04-08 05:11:58 PST --- I know about the LIMIT_BUFFER option but I don't like it. My intention is to decrease time spent on Garbage Collection but the LIMIT_BUFFER=true seems to do exactly opposite - my understanding is that it would mean allocation and releasing big buffer basically on every request. I don't think the report is invalid, JSP servlet has intention to release the page context at the end. And the fact that big number of page contexts hang up in the memory after being released only because of references from tag handlers is something that should be fixed - no matter whether each such page context references 1MB buffer or not. And I think the fix should not be that hard - it should be just about removing reference between tag handlers and page contexts after tag handler does the job (as I see in the code whenever tag handler starts doing it's job first thing done is setting page context and parent). I'll try to create test webapplication, jmeter based test scenario and jhat oql statements showing the problem. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- 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
