[ http://issues.apache.org/jira/browse/JAMES-134?page=comments#action_63590 ] Vincenzo Gianferrari Pini commented on JAMES-134: -------------------------------------------------
First of all, reasonable maximum message sizes for an SMTP server should be quite below the values we are talking about here: SMTP != FTP. IMHO talking about 1 GB message size (or even 100 MB) is out of reality (remember to add about 33% to the attachment size to get the real message size). Secondly, DON'T USE INCREMENTAL GARBAGE COLLECTION (-Xincgc) with James (at least with jre 1.4.2_07 under linux, and <protocol>file</protocol>), as the effect in a real system is to slowly increase the average used memory, with an increasing "sawtooth" pattern, that will get in few hours to an OutOfMemory error. And this happens with a maximum message size limit set to values around 40MB. Instead, without -Xincgc, the behaviour is just an increase up to a reasonable horizontal asymptote. This does not mean that there may not be a memory leak somewhere in James: I recall (not sure though) something said by Noel about that when using the file protocol. > Large emails in the spool cause SpoolManager to throw OutOfMemoryError > ---------------------------------------------------------------------- > > Key: JAMES-134 > URL: http://issues.apache.org/jira/browse/JAMES-134 > Project: James > Type: Bug > Components: SpoolManager & Processors > Versions: 2.2.0, 2.0a3, 2.1.3, 2.1 > Environment: Operating System: MacOS X > Platform: Macintosh > Reporter: Matt Bishop > Attachments: TestMemRec.java > > Steps to repro: > 1. Send yourself a very large email (16 megs works for me) > 2. check the SpoolManager log and see this over and over: > ERROR spoolmanager: Exception in JamesSpoolManager.run null > java.lang.OutOfMemoryError > What makes this problem particularly bad is that the spoolmanager doesn't > move on to other > messages but keeps pegging the CPU trying to process this email. To fix it, > I have to shut down > james, delete the email files out of spool and restart. > EXPECTED: email should spool to the user as expected. -- 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]
