[ http://issues.apache.org/jira/browse/JAMES-592?page=comments#action_12433786 ] Stefano Bagnara commented on JAMES-592: ---------------------------------------
If you believe the problem is in the log rotation you may want to try replacing the DefaultLoggerManager with ExtendedLog4jLoggerManager in your kernel.xml. If the problem is in logkit or in its manager it won't leak anymore. > James leaks memory slowly > ------------------------- > > Key: JAMES-592 > URL: http://issues.apache.org/jira/browse/JAMES-592 > Project: James > Issue Type: Bug > Affects Versions: 2.3.0rc3, 2.3.0rc2 > Reporter: Norman Maurer > Assigned To: Noel J. Bergman > Priority: Critical > > 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 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
