[ http://issues.apache.org/jira/browse/JAMES-134?page=all ]
OG updated JAMES-134:
---------------------
Attachment: JamesMimeMessage.java
Hi All,
The new file I have attached (Second today) is working :)
I have compiled it, and ran some big test files through a test account in the
new server. The server ran all the time with under 27 MB of virtual memory
footprint from which under 10 MB were physical RAM usage. The big test files
sizes were 30 MB and 187 MB.
Hip Hip ::))
There are more details in the first comments of the file.
> 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: JamesMimeMessage.java, JamesMimeMessage.java, 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]
