I don't know if this has been mentioned but we developed a multi-threaded
app and had OutOfMemoryError problems similiar to yours. The culprit was
the 1.1.5 jdk (had thread memory leak problems). After upgrading the jdk
our problems went away.
Robert
Mehrdad Jahansoozi wrote:
> This is usual
This is usual in multithreaded programs
There are two solutions to these sorts of problems
1) Limit the number of threads to 5 at any time.
2) Write the data on a temporary files and read it later.
Which one is a mater of time ( speed ).
If you are reading over a network, pipe the data directly
> I am running into a problem where my vm grows too big, to fast (faster than the
> consumers of the collected data can consume it), resulting in a
> OutOfMemoryError in all running threads. I changed the vm to run with -mx50m
> and it ran for much longer (about 5 days) then it too did the same t
ay to get the maximum heap size from inside java. I though that
> Runtime.totalMemory() would return that, but it does not. I current am running
> one vm with -mx50m and totalMemory() is returning 5242872, which is about 5mb
> not 50mb... unless I am totally crazy.
>
> I am running into
Is there any way to get the maximum heap size from inside java. I though that
Runtime.totalMemory() would return that, but it does not. I current am running
one vm with -mx50m and totalMemory() is returning 5242872, which is about 5mb
not 50mb... unless I am totally crazy.
I am running into a
