Re: Outrigger memory leak?

John McClain - Sun Microsystems, Inc. wrote:
> Random thought - Java will throw OoME for other conditions besides
> running out of memory, it could have memory but no block is big enough
> to satisfy the requested allocation, it could be out of threads (seems
> unlikely that would be the case here though). Don't suppose there is any
> sort of useful stack trace from the OoME?

I was going to ask about other memory needs such as stack, and non-heap memory.
  Running with jconsole or using a profiler to see which segments of memory are
having problems might be good.  Also, as of 1.5.0_04, there is a command line
flag to get a heap dump which might be helpful as well.

I use the YourKit Java profiler because the price is right and it runs remotely
just fine and you can start the JVM with the facility available, but not active,
and then remotely turn it on and off.

Gregg Wonderly

===========================================================================
To unsubscribe, send email to [email protected] and include in the body
of the message "signoff JAVASPACES-USERS".  For general help, send email to
[email protected] and include in the body of the message "help".

To view past JAVASPACES-USERS postings, please see:
http://archives.java.sun.com/archives/javaspaces-users.html