Hello
We are experiencing a garbage collection problem. We are running Orion
1.4.7 on a Linux 2.4 box. We have been trying the Sun 1.2.2, the Sun 1.3
and the IBM JVM 1.3. On the Sun 1.3 JVM we have tried normal garbage
collection and also -Xincgc incremental garbage collection. We run with
500 megabytes of heap space available to Java.
The system uses lots of EJBs (mainly stateless session but also quite a
few entities and a handful of stateful session beans), and we have JSP
pages which run in the same JVM.
The system runs very responsively and well, with up to 90 users
simultaneously using it, for up to an hour. Then enormous GCs start
happening which block all activity for up to 180 seconds at a time! The
length and frequency of the freezes vary with the different JVMs but all
are unusable after say an hour of up time.
The Sun 1.3 in incremental GC mode is the best, and in fact remains stable
and usable until it starts doing a few 9 second GCs from time to time
(comparatively bearable) until we get a "HotSpot internal error" which
stops all processing.
We are trying all sorts of different things to stop our users getting
upset, like reducing the JSP session timeout to a minimum, and are
currently trying to analyse the code with JProbe to find out how to
minimise unnecessary object creation or memory leaks (stale references to
no longer used objects etc).
As several list members have already said, it also seems that some beans
are never passivated.
What can we do to make Orion stop using more and more memory, and not to
cause such outrageous garbage collection cycles?
Any comments or suggestions would be very much appreciated.
--
Thomas Munro <[EMAIL PROTECTED]>
http://www.fullsix.com/
Fullsix Technology (Paris)
