be careful with interpreting this value. the JVM is _not_ required to release memeory as soon as it is no longer referenced! so (maybe) it keeps appearing under "memoryUsed" although it _could_ be garbage collected.
this value gets very interesting as soon as you hit the ceiling. when mem becomes rare, the JVM _is_ required to free all memory it possibly can. if it can't, you get OutOfMem exceptions. (but this can also mean that the heap is not big enough for the mail load.) if, after a long, long run-time (a few days) under constant load the OOM pops up, I think it is safe to say there is a leak. I'd like to see James converge asymptotically against an upper bound for "memoryUsed" which is fairly below "memoryMax". Bernd On 8/22/06, Norman Maurer <[EMAIL PROTECTED]> wrote:
After running postage now about 3 hours with dbfile the used memory jump from 43mb to 51mb. Just to keep you guys up to date. bye Norman Am Dienstag, den 22.08.2006, 12:12 +0200 schrieb Norman Maurer: > Can you run a postage test with dbfile and one with mysql ? > > bye > Norman > > > Am Dienstag, den 22.08.2006, 03:07 -0700 schrieb Bernd Fondermann > (JIRA): > > [ http://issues.apache.org/jira/browse/JAMES-592?page=comments#action_12429665 ] > > > > Bernd Fondermann commented on JAMES-592: > > ---------------------------------------- > > > > Maybe we can confirm a db/mysql specific problem by running identical scenarios on file/derby/mysql and compare mem consumption. > > At best, the scenario would mimmick Noel's production load (scaled up, to accelerate the process), if he likes to disclose this information. > > > > > James leaks memory when using MYSQL > > > ----------------------------------- > > > > > > Key: JAMES-592 > > > URL: http://issues.apache.org/jira/browse/JAMES-592 > > > Project: James > > > Issue Type: Bug > > > Reporter: Norman Maurer > > > Assigned To: Norman Maurer > > > Priority: Blocker > > > Fix For: 2.3.0 > > > > > > > > > Noel wrote on list: > > > I do not know where in the application it is happening, but after running > > > JAMES non-stop since Fri Aug 11 03:29:57 EDT 2006, this morning the JVM > > > started to throw OutOfMemoryError exceptions, such as: > > > 21/08/06 08:39:47 WARN mailstore: Exception retrieving mail: > > > java.lang.RuntimeException: Exception caught while retrieving an object, > > > cause: java.lang.OutOfMemoryError, so we're deleting it. > > > That did not recover, so it wasn't just due to a transient large allocation > > > (which I limit, anyway), so there is definitely something leaking, albeit > > > slowly. Keep in mind that the store was one of the victims, but not > > > necessarily the cause. > > > The JVM process size had steadily grown from a somewhat stable 114MB to > > > 130MB last night. I did not look at it this morning before restarting the > > > server. > > > --- Noel > >
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
