In article <f8vhbe$94q$1@forums.macromedia.com>
"rich.leach"
<webforumsuser@macromedia.com> wrote:
> came back fine. However, I tracked the memory usage on
my server and
> noticed that jrun.exe climbed all the way up to close to
1 gb (I
> adjusted the min/max heap settings in the CF Admin to
allow that) but
> JRUN never let go of all that memory, it's continuing to
ping at
> close to 1 gb.
That's standard behavior for a Java application in general.
Java
performs its own memory management and if you tell it there's
1Gb heap
it will allocate that memory from the operating system if
needed but
then it will manage its own needs within that 1Gb of
allocated space.
If you look at the JVM memory usage directly, you'll see it
isn't
using much memory after your page has run (because garbage
collection
returns it to the heap) but the heap memory all belongs to
Java so the
operating system shows it as still allocated.
Hope that explains it?
Sean A Corfield
An Architect's View --
http://corfield.org/
--
I'm using an evaluation license of nemo since 61 days.
You should really try it!
http://www.malcom-mac.com/nemo