Name: ssT124754 Date: 02/28/2001
java -ms64m -mx300m
This post is related to bug #4140301. I have implemented a "MemoryThread" API
that implements the notion of "red/yellow/green" memory zones for the heap. The
one major flaw in all of this though is that it relies on the maxmimum heap size
specified in java -ms64m -mx[MAX HEAP]m in the command line to also be specified
in a config file. If we could get this parameter at runtime, then life would be
great! BTW, the API that I have implemented is not perfect, but it does do the
job correctly. (Well...so far). It's too bad that they made you guys pull the
API, as I'm sure your version would be much more robust/reliable than that which
I have implemented. It also seems sort of awkward since Java seems to be
dominating the server-side market, but this memory problem is of direct import
to this area. I have seen many "Java partners" that have implemented Java
products throwing OutofMemory errors. Is there an appropriate place that I could
submit my source-code so that others may benefit from its use? Apache seems
pretty tied up with Servlet/Mail etc... developments. Ah well, If anyone wants
it, just e-mail me.
(Review ID: 117607)
======================================================================
- duplicates
-
JDK-4349850 java.lang.Runtime.maxMemory()/availableProcessors()
-
- Resolved
-
- relates to
-
JDK-4429987 Give java apps the ability to "suggest" their own max-heapsize
-
- Closed
-