Tuesday, January 5, 2010

Yourkit Java Profiler License Key Java Memory Leak Disapears While Using A Profiler.?

Java memory leak disapears while using a profiler.? - yourkit java profiler license key

I have a Java web application on Tomcat is leaking memory.

When I launch the application, fill quickly, as a rule and hammer the ball to inquiries, 600 MB RAM, if the JVM seems to hang.

However, when I run Profiler (YourKit Java Profiler) disadvantages, the memory usage is a constant, 81MB RAM, not the top, regardless of the number of requests of IT processes.

It seems that the implementation of a profile-term memory compared to my request for memory loss, so it is difficult to determine.

There seems to be differences in the arguments command line with tomcat normally and with the profiles, and in both cases I have that same JDK (1.6.0_03) bin

Anyone have any ideas?

3 comments:

Irony Man said...

You need to configure Tomcat

Go to configure Tomcat

In the properties for Apache Tomcat

Tab [Java]

First series of 64 MB of memory
and the maximum memory to 192 MB

Garbage collection will be released to free memory back when it came to 192 MB.

Date updated:
Sun JVM is not optimized.
You need to tune in to see the site.

http://www.folgmann.com/en/j2ee/gc.html

rohit yadav said...

Tomcat doesnot handle memory leaks and dangling objects YourKit Java Profiler, but it has built in to optimize the memory usage and prevent memory loss due to the release of unused memory ....
The program should be a terrible loss, if memeory CPU usage varies in the range of 600 to 81 MB
try to use free memory System.gc () and ensure close DB connections and that no objects are used unnecessarly

rohit yadav said...

Tomcat doesnot handle memory leaks and dangling objects YourKit Java Profiler, but it has built in to optimize the memory usage and prevent memory loss due to the release of unused memory ....
The program should be a terrible loss, if memeory CPU usage varies in the range of 600 to 81 MB
try to use free memory System.gc () and ensure close DB connections and that no objects are used unnecessarly

Post a Comment