[ http://issues.apache.org/jira/browse/JAMES-134?page=comments#action_12362835 ]
Stefano Bagnara commented on JAMES-134: --------------------------------------- Few months ago I replaced the InputStreams used by James in mimemessages constructors to SharedByteArrayInputStreams but It didn't solve the memory issue. Maybe you could elaborate more on your proposal and provide a test and a patch for the issue. > 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.1, 2.1.3, 2.0a3, 2.2.0 > 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]
