Alex, IMHO it appears you have a memory leak that is not necessarily a
JVM issue.
But while we are on the GC topic:
Does the 1.4 JVM 'stop the world', or pause *all* threads
while it does a GC. This tends to have a negative impact on
real-time Java Apps on SMP boxes.
I heard a concurrent-collector was sourced in the 1.4 'merlin'
J2SE for solaris.
thanks,
will
-----Original Message-----
From: Alexandre Goncalves [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 20, 2002 5:18 AM
To: [EMAIL PROTECTED]
Subject: garbage collection
hi.
We're having a problem with garbage collection in our web site.
We're using JRun with j2sdk 1.4.0 running on a linux machine. The
problem is that after we launch the jrun server the memory starts to
increase up to the maximum heap size defined (1G in our case). When it
reaches this memory amount, the site simply "dies": basically it does
not give any response.
What we do to overcome this situation is a restart of the jrun servers,
"cleaning" the java virtual machine.
We also tried to call periodically System.gc() but it didn't produced
any visible results so we aborted this approach.
Does anyone knows a way to avoid this situation?
Thanks in advance.
Best regards,
Alexandre Gonçalves.
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
