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