Maybe my question sounded too vague and repetitive. What I meant is something like this "Is the a class loader (or something like that) than I should start analyzing? I mean, is there a route I should follow in order to see which objects are stucked? If the Tomcat Manager knows that something got stucked in the memory, how does it know that? Is there a clue we should start?".
> -----Original Message----- > From: Brian [mailto:bbprefix-m...@yahoo.com] > Sent: Monday, November 15, 2010 10:58 PM > To: users@tomcat.apache.org > Subject: After manager says that there was a leak, how to use a profiler? > > Hi, > > > > After the Tomcat manager warns that there was a leak with one app what was > stopped or undeployed, how do I use the profiler to investigate that? I mean, > that is the starting point to analize that? What should I look for? > > > > Brian > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
