You may find some of the JavaOne 2009 session presentations useful for
dealing with these kinds of problems such as...
"Monitoring and Troubleshooting Java Platform Applications with JDK
Software" (BOF-4724)
http://blogs.sun.com/nbprofiler/entry/javaone_2009_slides_monitoring_and
"Monitoring and Troubleshooting GlassFish Application Server in the
Wild" (Community One)
don't have a link, sorry, assume it is posted online, check the aquarium?
Also, VisualVM 1.2.2 was just released a few days ago which might be helpful:
http://blogs.sun.com/nbprofiler/entry/visualvm_1_2_2_released
Wayne
On Tue, Jan 12, 2010 at 7:53 AM, Alexis Moussine-Pouchkine
<alexis.mp_at_sun.com> wrote:
> The data I was looking for is "java.lang.OutOfMemoryError: Java heap space"
> I trust the GC to do its work properly and I sounds like you need to chase a memory "leak".
> A profiler like yourkit should help you track objects that are not GC'd on explicit calls to the GC but it's likely that you will need a developer familiar with the application.
> -Alexis
>