Thanks a lot for the Tip. Eclipse MAT helped a lot!
All the best to all of you!! On Fri, Jul 4, 2008 at 5:56 AM, Surendrakumar Viswanathan -X (suviswan - HCL at Cisco) <[EMAIL PROTECTED]> wrote: > Hi > Add -XX:+HeapDumpOnOutOfMemoryError option to you JVM parameter. It > will dump the heap (in hprof format) on OOM. You can take the hprof file > and then analyze using Eclipse MAT (Memory Analyzer tool). This will > give you information on which objects are getting used most. Based on > that you can find out the corresponding application code and check > whether there are memory leak exists in the code. > The random slowness is usually associated with GC. Enable verboseGC > with timestamp option and then check whether the GC is happening at the > corresponding time of slowness. > > Suren > >> -----Original Message----- >> From: Maduranga [mailto:[EMAIL PROTECTED] >> Sent: Friday, July 04, 2008 3:22 AM >> To: Tomcat Users List >> Subject: Re: Tomcat Runs OutOfMemory (Not at repeated WAR deployments) >> >> Its 32 bit. Sorry I missed that earlier. >> >> Could be a problem with web app. Could you give me an >> idea/example for a profiler? Any open source ones available? >> >> I am really in a tight schedule to get this sorted out. All >> the help much appreciated Thanks a lot >> >> Maduranga >> >> >> On Thu, Jul 3, 2008 at 6:13 PM, Caldarale, Charles R >> <[EMAIL PROTECTED]> wrote: >> >> From: Maduranga [mailto:[EMAIL PROTECTED] >> >> Subject: Re: Tomcat Runs OutOfMemory (Not at repeated WAR >> >> deployments) >> >> >> >> OS: Red Hat Enterprise Linux AS release 4 (Nahant Update 2) >> > >> > Is that 64-bit or 32-bit? >> > >> >> I have 2G ram for JVM, but I would like to stick with 1G if its >> >> possible. >> > >> > If that's 2G for the entire JVM process, the maximum heap >> you can get away with would be somewhere around 1.5G, since >> there's a fair amount of space needed for code, libraries, >> file space, etc. >> > >> >> Do you recommend upgrading to Tomcat 6? >> > >> > Might have some benefit, but you really need to run a >> profiler to find out what's consuming the memory. The >> problem is likely to like with your webapp, not Tomcat itself. >> > >> > - Chuck >> > >> > >> > THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR >> OTHERWISE PROPRIETARY MATERIAL and is thus for use only by >> the intended recipient. If you received this in error, please >> contact the sender and delete the e-mail and its attachments >> from all computers. >> > >> > >> --------------------------------------------------------------------- >> > To start a new topic, e-mail: users@tomcat.apache.org To >> unsubscribe, >> > e-mail: [EMAIL PROTECTED] >> > For additional commands, e-mail: [EMAIL PROTECTED] >> > >> > >> >> >> >> -- >> Maduranga >> >> --------------------------------------------------------------------- >> To start a new topic, e-mail: users@tomcat.apache.org To >> unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Maduranga --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
