geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vamsavardhana Reddy" <c1vams...@gmail.com>
Subject Re: How to get memory statistics from a remote Geronimo runtime?
Date Fri, 07 Dec 2007 17:27:55 GMT
On Dec 7, 2007 9:38 PM, Matt Hogstrom <matt@hogstrom.org> wrote:

>
> On Dec 5, 2007, at 4:29 AM, Vamsavardhana Reddy wrote:
>
> >
> >
> > On Dec 4, 2007 11:23 PM, Anita Kulshreshtha <a_kulshre@yahoo.com>
> > wrote:
> >   It is not clear to me if this is part of the earlier code or a
> > separate program. If it is part of the JMX code, then Runtime is from
> > the local jvm not remote. The non heap Memory for this program in
> > either case is negligible.
> >   You could start G with -Dcom.sun.management.jmxremote. Start
> > jconsole and click on the Memory tab to get the whole picture.
> > I have started G with the said option and hooked up jconsole.  The
> > HeapMemoryUsage is showing exactly what Runtime is returning.
> >
> > It is only the heap memory exhaustion that results in OOME.  I guess
> > I am ok for now as this is what I am interested in.
> >
>
> One will get OOM Exceptions if there is insufficient native memory to
> satisfy a Java request.  For instance, when creating a thread, the OS
> has to allocate some native memory to create the Java Object. If that
> native allocation fails you will get an OOM even though you have
> plenty of heap memory.

You are right.  Any ideas on how to figure if we are exhausting that native
memory?

Mime
View raw message