https://bz.apache.org/bugzilla/show_bug.cgi?id=69608
--- Comment #7 from John Engebretson <jeng...@apache.org> --- I agree with others that this probably isn't caused by an error in Tomcat - Tomcat directly allocates a relatively small amount of memory, so whatever is creating the GC demand is most likely application code. The best way to investigate that is to collect a heap dump (look up "jmap" in the JDK) and look to see what objects or classes are using up the heap. Eclipse MAT is a good tool here. If you find that Tomcat code is at fault, please add that info to this ticket. Otherwise you may find better information from general Java resources about memory and GC optimization. -- 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
