On 28/07/2011 12:29, Ian Marsh wrote: > Right, I have taken a memory snapshot using YourKit of the system > running Tomcat-7.0.10 after about 1 hour, when the Old Gen memory was > beginning to reach its maximum.
OK. I think a little more digging is required but this might be heading somewhere useful. > So I looked into the "Selected Objects" of the > java.util.concurrent.ConcurrentHashMap$Segment[16]. This contains... > > + java.util.concurrent.ConcurrentHashMap$Segment[16] (732,561,032) > =+ [14] java.util.concurrent.ConcurrentHashMap$Segment (55,193,864) > ==+ table java.util.concurrent.ConcurrentHashMap$HashEntry[512] (55,193,792) > ===+ [16] java.util.concurrent.ConcurrentHashMap$HashEntry (496,712) > ====+ value org.apache.jasper.servlet.JspServletWrapper (496,448) Filter for objects of org.apache.jasper.servlet.JspServletWrapper and trace where the bulk of the retained size is for the few largest. That should move things forward a little. The level of detail in here is about right. Enough to see where to go next, not so much it takes ages to analyse. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
